[dtrace-discuss] DTrace under Linux

[陶捷 (Euler Tao)]

Thanks, I understand now.

er... I've planed to read the source code of DTrace. I think it may be
consisted of two parts, the kernel of Dtrace and the 30K+ providers.
And is the main code of DTrace in a separate directory in the whole kernel
code tarball, e.g. on-src-b56.tar.bz2.
I've searched the key word, "dtrace", in the web page,
http://cvs.opensolaris.org/source/.
And I was confused by the results. They looked a little disordered.

I have no experience on reading any Solaris's Codes yet.
Can someone do me a favor? Give me some hints.

Thanks!

Regards

T.J.


2007/2/14, Casper.Dik at sun.com <Casper.Dik at sun.com>:
>
>
> >Why do you say that SystemTap only is done on i386?
> >Does it means that, compared with DTrace, SystemTap is focused more on
> >hardware infomation?
>
> Dynamic kernel probing tools like DTrace need to understand and modify
> the instruction streams in the kernel.
>
> >Does DTrace has two different kernel parts?
> >I means for the x86 and SPARC architecture, there're something different
> >inside the 2 DTraces?
>
> Yes; DTrace is atypical in that it requires quite intimate knowledge
> of how instruction streams work.  But from a user's perspective this
> is all hidden and you can use the same scripts on both architecture.
>
> The DTrace architecture limits the knowledge of the processor architecture
> to the DTrace to the providers which need that knowledge (such as the
> fbt and fasttrap provider)
>
> Sun has a requirement for "completeness", i.e., support for all
> architectures,
> when putting a project in Solaris.  That's why we have support for DTrace
> on all supported platforms.
>
> In Linux, it is possible that systemtap becomes mainstream without support
> for other architectures.  (Systemtap is also much more limited and does
> not
> make the safety guarantees DTrace makes)
>
> Casper
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070214/de4bd02a/attachment.html