Hey Chris,
Chris Rijk wrote:
I don't have any comments about the suggested implementation.
However, what would be the downsides of integrating CPC collection into the
kernel - so that CPC registers are a constant part of a LWP's state. So when
a LWP starts running on a particular CPU core, the
Sorry for jumping back into this discussion so much later...
Jonathan Adams wrote:
On Wed, Mar 08, 2006 at 11:32:05AM -0800, WILLIAM CHEN wrote:
In response to the question of what happens if the buffer never
overflows. One will not get an interrupt if the buffer does not
overflow. In this ca
The way I had prototyped it only requires minor changes to the current libcpc
structure support. All the underlying functionality and code are already in
the kernel.
1. All the cpc data structures are already available. Only addition to support
buffering is adding the buffer array into the st
I don't have any comments about the suggested implementation.
However, what would be the downsides of integrating CPC collection into the
kernel - so that CPC registers are a constant part of a LWP's state. So when a
LWP starts running on a particular CPU core, the CPC counters are set to zero,
On Wed, Mar 08, 2006 at 11:32:05AM -0800, WILLIAM CHEN wrote:
> In response to the question of what happens if the buffer never
> overflows. One will not get an interrupt if the buffer does not
> overflow. In this case, the event being monitored is very rare
> or the application being monitored h
Thread id is very useful information to include also.
William
This message posted from opensolaris.org
___
perf-discuss mailing list
perf-discuss@opensolaris.org
In response to the question of what happens if the buffer never overflows. One
will not get an interrupt if the buffer does not overflow. In this case, the
event being monitored is very rare or the application being monitored has a
very short execution time. In either case, the overhead of th
