Hi,
The dtrace maillist said cpc provider had arrived into snv_109. But after I
build snv_109 kernel, it seems cpc provide isn''t in it. On intel Q6600
host.
#cat ex1.d
#!/usr/sbin/dtrace -s
cpc:::inst_retired-10000
{
@[execname] = count();
}
# ./ex1.d
dtrace: failed to compile script ./ex1.d: line 3: probe description
cpc:::inst_retired-10000 does not match any probes
Does snv_109 support cpc provider?
thanks
jin
--
This message posted from opensolaris.org
Jin wrote:> Hi, > > The dtrace maillist said cpc provider had arrived into snv_109. But after I build snv_109 kernel, it seems cpc provide isn''t in it. On intel Q6600 host. > > #cat ex1.d > #!/usr/sbin/dtrace -s > > cpc:::inst_retired-10000 > { > @[execname] = count(); > } > > # ./ex1.d > dtrace: failed to compile script ./ex1.d: line 3: probe description cpc:::inst_retired-10000 does not match any probes > > Does snv_109 support cpc provider? > > thanks > jinI don''t know a lot about the cpc provider, but http://blogs.sun.com/jonh/entry/finally_dtrace_meets_the_cpu seems to imply you need the "Mode" part of the probe name...that is, inst_retired-X-10000 (where X is sys, user, or all)
Hi Jin,> # ./ex1.d > dtrace: failed to compile script ./ex1.d: line 3: probe description cpc:::inst_retired-10000 does not match any probes > > Does snv_109 support cpc provider?Yes, the provider is in snv_109 and, as Dan says, you need to specify a mode. You may know this anyway as you''re using a platform specific event name in the example you cite; the core performance counter back end (which I think you''ll be using here with the Q6600) doesn''t support any generic event names at the minute. It''s on someone''s todo list. Hopefully he''s reading this ;-) . Jon.