I would first try prtconf -v to see if the bus speed is listed as a property of
the bus' driver.
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Thanks for spelling that out what you were working with.
As a matter of style, splitting the test logic across probe declarations sure
would be easier to read (and reread).
All that opt_* test logic in one predicate requires the maintainer to
understand the preamble. For example, when is OPT_c
> Oh, I see, Thanks. Can I then copy all the data that I need from the
> copied structure into "this" variables in the clause where copyin is
> called, and then use the values in subsequent clauses (that correspond
> to the same probe)? e.g.:
>
Yes.
Chip
you can do
pid$target::foo:entry
/ (this->dataP = (ProfData*)copyin(arg2, sizeof(ProfData))->execTime > 100/
{
@longTx[arg0] = count();
}
--chris
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.or
Oh, I see, Thanks. Can I then copy all the data that I need from the
copied structure into "this" variables in the clause where copyin is
called, and then use the values in subsequent clauses (that correspond
to the same probe)? e.g.:
pid$target::foo:entry
{
this->dataP = (ProfData*)copyin(ar
The extra copyin is required as copyin returns scratch memory and scratch
memory so is only valid in that clause.
--chris
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Thanks a lot!
Another mistery solved.
-Original Message-
From: jonathan.has...@sun.com [mailto:jonathan.has...@sun.com]
Sent: Friday, September 18, 2009 12:21
To: Sloot, Hans-Peter
Cc: dtrace-discuss@opensolaris.org
Subject: Re: [dtrace-discuss] Why is plockstat provider only present fo
Does the same apply for the pid provider?
I have seen pid providers with dtrace -l.
At the moment the command does not list any pid providers.
Yes, pid provider probes won't appear in the ouput of `dtrace -l`
until they have been explicitly created (by enabling them):
# dtrace -l -P pid*
I
Hi Jon,
Does the same apply for the pid provider?
I have seen pid providers with dtrace -l.
At the moment the command does not list any pid providers.
Regards Hans
-Original Message-
From: jonathan.has...@sun.com [mailto:jonathan.has...@sun.com]
Sent: Friday, September 18, 2009 11:30
Ok thanks.
It works!
-Original Message-
From: jonathan.has...@sun.com [mailto:jonathan.has...@sun.com]
Sent: Friday, September 18, 2009 11:30
To: Sloot, Hans-Peter
Cc: dtrace-discuss@opensolaris.org
Subject: Re: [dtrace-discuss] Why is plockstat provider only present for
1 process
Hi
Hi Hans,
I would like to know why dtrace -l |grep plockstat show plockstat28099
lines.
Process with pid 28099 is a java process.
Why can I not examine other processes with the plockstat provider?
Is it a java startup option?
No. The probes that plockstat uses only become visible when you
ac
Sloot, Hans-Peter wrote:
Hi,
Can someone explain the difference between the lockstat and plockstat
provider?
lockstat is for the kernel. plockstat is for user 'p'rocesses.
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Hi,
Can someone explain the difference between the lockstat and plockstat
provider?
Regards Hans
ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n
g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l
b e s t e m d v o o r d e g e a d r e s s e e r d
Hi,
I would like to know why dtrace -l |grep plockstat show plockstat28099
lines.
Process with pid 28099 is a java process.
Why can I not examine other processes with the plockstat provider?
Is it a java startup option?
Regards Hans
ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n
14 matches
Mail list logo
