Hey, Jon, On Mon, Jul 14, 2008 at 5:42 AM, Jon Haslam <[EMAIL PROTECTED]> wrote: > 3. Co-existence with existing tools > > The provider has priority over per-LWP libcpc usage (i.e. cputrack) > for access to counters. In the same manner as cpustat, enabling probes > causes all existing per-LWP counter contexts to be invalidated. As long as > these enablings remain active, the counters will remain unavailable to > cputrack-type consumers. > > Only one of cpustat and DTrace may use the counter hardware at any one time. > Ownership of the counters is given on a first-come, first-served basis.
I'm curious, how does DTrace interact with DTrace in this situation? Specifically, if two DTrace invocations (either separate D scripts or even two clauses in the same D script) specify the same hardware counter in a probe, will they both see (effectively) the same data, or will the first invocation be the only one to see useful data? Chad _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
