BTW, you can use the command "mpstat" inside the simulated system
to tell you a rough idea on break down of user/kernel/waiting/idle
times.
I think the new utility, DTrace, also can do this. But I don't know
more details.
On Thu, 03 Mar 2005 Weihang Jiang wrote :
> Hi,
> I want to break down execution cycles into different categories:
> user cycles, kernel cycles, privilage instructions cycles and idle
> cycles. (as in Memory System Characterization of Commerical
> Workloads).
>
> I found something from ruby0.dump-stat :
> Resource Usage
> --------------
> page_size: 4096
> user_time: 1334
> system_time: 29
>
> Is it the right place to look at?
>
> TIA
>
> --
> Weihang Jiang
> _______________________________________________
> Gems-users mailing list
> Gems-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
|