Dear All:
I heard that the Solaris'' powerful tool, DTrace have been
ported
into Linux platform.
What''s the name of that project? Where could I find its
homepage?
And what''s the name of this new linux tool.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070213/399f9b61/attachment.html>
Dear All:
I heard that the Solaris'' powerful tool, DTrace have been
ported
into Linux platform.
What''s the name of that project? Where could I find its
homepage?
And what''s the name of this new linux tool.
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070213/f562da56/attachment.html>
DTrace has not been ported to Linux, but DTrace is available for Linux applications at least in a limited sense. Using BrandZ you can run Linux binaries on a Solaris system and use DTrace to examine its behavior. http://blogs.sun.com/ahl/entry/dtrace_for_linux http://blogs.sun.com/ahl/entry/dtrace_at_scale_4x Adam On Tue, Feb 13, 2007 at 12:38:04AM +0800, (Euler Tao) wrote:> Dear All: > > I heard that the Solaris'' powerful tool, DTrace have been ported > into Linux platform. > What''s the name of that project? Where could I find its homepage? > And what''s the name of this new linux tool. > > Thanks!> _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org-- Adam Leventhal, Solaris Kernel Development http://blogs.sun.com/ahl
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? And it leads another question. Does DTrace has two different kernel parts? I means for the x86 and SPARC architecture, there''re something different inside the 2 DTraces? thanks a lot :) Regards T.J. 2007/2/14, Damian Wojslaw <damian at wojslaw.pl>:> > On Tue, 2007-02-13 at 00:37 +0800, ?? (Euler Tao) wrote: > > Dear All: > > > > I heard that the Solaris'' powerful tool, DTrace have been > > ported into Linux platform. > > What''s the name of that project? Where could I find its > > homepage? > > And what''s the name of this new linux tool. > > It wasn''t and it probably will not be. Linux developers are coming with > their own tool called systemtap, which homepage can be found here: > http://sourceware.org/systemtap/ but as far as I know it lacks support > for userland probing, works for this feature are only being done on i386 > architecture and it''s documentation isn''t as extensive as DTrace. > > Regards > > Damian Wojslaw > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070214/e3861b4f/attachment.html>
>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
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>
>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.There are only a handful of providers; but each provider can provide 1000s of probe points (specifically the fbt provider).>And is the main code of DTrace in a separate directory in the whole kernel >code tarball, e.g. on-src-b56.tar.bz2.You can browse the source through cvs.opensolaris.org>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.That''s what search engine do for you. There''s an index page which explains some of what source lives where. Casper
I''ve read the dtrace usenix paper already. At the end of this paper, the authors said that one of the future work was the "performance counters". Has this been implemented in the current DTrace? Regards T.J. 2007/2/14, Sean McGrath - Sun Microsystems Ireland <sean.mcgrath at sun.com>:> > ???? (Euler Tao) stated: > < 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. > > Dtrace may look ''disordered''. You''re probably finding all the > dtrace probes points etc that are scattered all over the place in various > modules, libraries etc. The bits that really make up the dtrace > framework > are better explained from Bryan''s blog, below. > > < > < I have no experience on reading any Solaris''s Codes yet. > < Can someone do me a favor? Give me some hints. > > Dtrace was the original bit of code that was opened up before the full > opensolaris, way back. Bryan''s blog gives us a tour of the dtrace code > from this initial code: > > http://blogs.sun.com/bmc/date/20050125 > > Its still good to go through this once in a while. > > That along with the dtrace usenix paper gives a good overview of how > dtrace works along with where it lives in opensolaris. > > http://www.sun.com/bigadmin/content/dtrace/dtrace_usenix.pdf > > That should help you get started :) > > Sean. > . > < > < 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 > < > > > < _______________________________________________ > < dtrace-discuss mailing list > < dtrace-discuss at opensolaris.org > > > -- > Sean. > . >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070214/cbb165ec/attachment.html>
Is DTrace talked about in the book, "Solaris Internals. Edition 2"? I haven''t got this book. But someone told me that this book maybe the most detail book about Solaris kernel code. 2007/2/14, Sean McGrath - Sun Microsystems Ireland <sean.mcgrath at sun.com>:> > ???? (Euler Tao) stated: > < 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. > > Dtrace may look ''disordered''. You''re probably finding all the > dtrace probes points etc that are scattered all over the place in various > modules, libraries etc. The bits that really make up the dtrace > framework > are better explained from Bryan''s blog, below. > > < > < I have no experience on reading any Solaris''s Codes yet. > < Can someone do me a favor? Give me some hints. > > Dtrace was the original bit of code that was opened up before the full > opensolaris, way back. Bryan''s blog gives us a tour of the dtrace code > from this initial code: > > http://blogs.sun.com/bmc/date/20050125 > > Its still good to go through this once in a while. > > That along with the dtrace usenix paper gives a good overview of how > dtrace works along with where it lives in opensolaris. > > http://www.sun.com/bigadmin/content/dtrace/dtrace_usenix.pdf > > That should help you get started :) > > Sean. > . > < > < 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 > < > > > < _______________________________________________ > < dtrace-discuss mailing list > < dtrace-discuss at opensolaris.org > > > -- > Sean. > . >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070214/c3002bcf/attachment.html>
On Wed, Feb 14, 2007 at 08:01:19PM +0800, ???? (Euler Tao) wrote:> I''ve read the dtrace usenix paper already. > At the end of this paper, the authors said that one of the future work was > the "performance counters". > Has this been implemented in the current DTrace?Not yet. regards, john
On 2/14/07, ?? (Euler Tao) <eulertao at gmail.com> wrote:> > 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? > > And it leads another question. > Does DTrace has two different kernel parts? > I means for the x86 and SPARC architecture, there''re something different > inside the 2 DTraces?No Dtrace has not been ported to Linux, Systemtap is as close as it gets. DTrace is currently limited to x86/64 and Sparc, Systemtap currently supports x86/64, PPC, and s390 with its sparc implementation as well as others platforms not as well tested or as far along. Systemtap has no userland probes so its unable to probe user apps, something that google has had for close to 3 years now. With that said Systemtap is not as stable even on x86/s86 its primary platform as Dtrace is. here are some links that compare DTrace and Systemtap http://uadmin.blogspot.com/2006/06/dtrace-vs-systemtap-for-administrator.html http://uadmin.blogspot.com/2005/09/systemtap-links.html http://uadmin.blogspot.com/2006/05/what-is-dtrace.html http://uadmin.blogspot.com/2006/09/systemtap-vs-dtrace-chart.html James Dickens uadmin.blogspot.com thanks a lot :)> > Regards > > T.J. > > 2007/2/14, Damian Wojslaw < damian at wojslaw.pl>: > > > > On Tue, 2007-02-13 at 00:37 +0800, ?? (Euler Tao) wrote: > > > Dear All: > > > > > > I heard that the Solaris'' powerful tool, DTrace have been > > > ported into Linux platform. > > > What''s the name of that project? Where could I find its > > > homepage? > > > And what''s the name of this new linux tool. > > > > It wasn''t and it probably will not be. Linux developers are coming with > > their own tool called systemtap, which homepage can be found here: > > http://sourceware.org/systemtap/ but as far as I know it lacks support > > for userland probing, works for this feature are only being done on i386 > > architecture and it''s documentation isn''t as extensive as DTrace. > > > > Regards > > > > Damian Wojslaw > > > > > > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070214/2e42b01e/attachment.html>
On 2/14/07, James Dickens <jamesd.wi at gmail.com> wrote:> > > > On 2/14/07, ?? (Euler Tao) <eulertao at gmail.com> wrote: > > > > 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? > > > > And it leads another question. > > Does DTrace has two different kernel parts? > > I means for the x86 and SPARC architecture, there''re something different > > inside the 2 DTraces? > > > > No Dtrace has not been ported to Linux, Systemtap is as close as it gets. > DTrace is currently limited to x86/64 and Sparc, Systemtap currently > supports x86/64, PPC, and s390 with its sparc implementation as well as > others platforms not as well tested or as far along. Systemtap has no > userland probes so its unable to probe user apps, something that google has > had for close to 3 years now. With that said Systemtap is not as stable even > on x86/s86 its primary platform as Dtrace is. >oops i meant to type something that DTrace has had for close to 3 years. serves me right for posting without caffeine on board. here are some links that compare DTrace and Systemtap> > http://uadmin.blogspot.com/2006/06/dtrace-vs-systemtap-for-administrator.html > > > http://uadmin.blogspot.com/2005/09/systemtap-links.html > > http://uadmin.blogspot.com/2006/05/what-is-dtrace.html > > http://uadmin.blogspot.com/2006/09/systemtap-vs-dtrace-chart.html > > > James Dickens > uadmin.blogspot.com > > > > > thanks a lot :) > > > > Regards > > > > T.J. > > > > 2007/2/14, Damian Wojslaw < damian at wojslaw.pl>: > > > > > > On Tue, 2007-02-13 at 00:37 +0800, ?? (Euler Tao) wrote: > > > > Dear All: > > > > > > > > I heard that the Solaris'' powerful tool, DTrace have been > > > > ported into Linux platform. > > > > What''s the name of that project? Where could I find its > > > > homepage? > > > > And what''s the name of this new linux tool. > > > > > > It wasn''t and it probably will not be. Linux developers are coming > > > with > > > their own tool called systemtap, which homepage can be found here: > > > http://sourceware.org/systemtap/ but as far as I know it lacks support > > > for userland probing, works for this feature are only being done on > > > i386 > > > architecture and it''s documentation isn''t as extensive as DTrace. > > > > > > Regards > > > > > > Damian Wojslaw > > > > > > > > > > _______________________________________________ > > dtrace-discuss mailing list > > dtrace-discuss at opensolaris.org > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070214/ecc41a69/attachment.html>
On Wed, 14 Feb 2007, ???? (Euler Tao) wrote: Please don''t top post.> Is DTrace talked about in the book, "Solaris Internals. Edition 2"?Yes, especially the 2nd volume subtitled "Solaris Performance and Tools".> I haven''t got this book. But someone told me that this book maybe the most > detail book about Solaris kernel code.No maybe about it: it IS the most detailed book about the Solaris kernel code! For userland apps, I recommend "Solaris Systems Programming"--but then given that I wrote it, that''s not too surprising... :-) -- Rich Teer, SCSA, SCNA, SCSECA, OpenSolaris CAB member President, Rite Online Inc. Voice: +1 (250) 979-1638 URL: http://www.rite-group.com/rich
On Wed, 2007-02-14 at 20:08 +0800, ?????? (Euler Tao) wrote:> Is DTrace talked about in the book, "Solaris Internals. Edition 2"? > I haven''t got this book. But someone told me that this book maybe the > most detail book about Solaris kernel code.You are talking about: http://www.sun.com/books/catalog/solaris_internals.xml This is definitely the book to learn about the Solaris kernel and how processes work in Solaris. Part two in particular: PART TWO: The Process Model Chapter 2: The Solaris Process Model Chapter 3: Scheduling Classes and the Dispatcher Chapter 4: Interprocess Communication Chapter 5: Process Rights Management For something that is pretty much all about DTrace, take a look also at: http://www.sun.com/books/catalog/solaris_perf_tools.xml Solaris Performance and Tools: Dtrace and MDB techniques for Solaris 10 and OpenSolaris. This book is *great*. It is the companion to Solaris Internals edition 2. I''ve learned a good bit with this book, highly recommended. As a side note, Jim Mauro, one of the author has just done 3 days up in Canada: http://www.exitcertified.com/newsandevents/eventdetails/2007/solaris_roadshow/ covering process tools and dtrace and mdb. Apparently this was quite an impressive session, some linux users in academia and the business world were impressed enough to want to take a look at Solaris, just because of dtrace. I believe this was the full length version of the presentation that George Wilson did at Sun Tech Days Atlanta, a real nice presentation too. I dont have a link for it, but I believe this presentation is available in open/star office presentation format. Or maybe just in pdf. Do take a look at that. Francois> 2007/2/14, Sean McGrath - Sun Microsystems Ireland > <sean.mcgrath at sun.com>: > ???? (Euler Tao) stated: > < 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. > > Dtrace may look ''disordered''. You''re probably finding all the > dtrace probes points etc that are scattered all over the place > in various > modules, libraries etc. The bits that really make up the > dtrace framework > are better explained from Bryan''s blog, below. > > < > < I have no experience on reading any Solaris''s Codes yet. > < Can someone do me a favor? Give me some hints. > > Dtrace was the original bit of code that was opened up > before the full > opensolaris, way back. Bryan''s blog gives us a tour of the > dtrace code > from this initial code: > > http://blogs.sun.com/bmc/date/20050125 > > Its still good to go through this once in a while. > > That along with the dtrace usenix paper gives a good > overview of how > dtrace works along with where it lives in opensolaris. > > http://www.sun.com/bigadmin/content/dtrace/dtrace_usenix.pdf > > That should help you get started :) > > Sean. > . > < > < 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 > < > > > < _______________________________________________ > < dtrace-discuss mailing list > < dtrace-discuss at opensolaris.org > > > -- > Sean. > . > > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org
Thanks Francois for sharing that. The material for those sessions can be found on the www.solarisinternals.com site (scroll down and look for "Solaris Internals & Performance Class Material"). For each of the 3 sessions I did in Canada, I came away from each grinning from ear-to-ear, recalling my favorite Bryan Cantrill quote - "With DTrace, I can walk into a room of hardened technologists and get them giggling". Thanks, /jim Francois Dion wrote:> On Wed, 2007-02-14 at 20:08 +0800, ?????? (Euler Tao) wrote: > >> Is DTrace talked about in the book, "Solaris Internals. Edition 2"? >> I haven''t got this book. But someone told me that this book maybe the >> most detail book about Solaris kernel code. >> > > You are talking about: > http://www.sun.com/books/catalog/solaris_internals.xml > > This is definitely the book to learn about the Solaris kernel and how > processes work in Solaris. Part two in particular: > PART TWO: The Process Model > Chapter 2: The Solaris Process Model > Chapter 3: Scheduling Classes and the Dispatcher > Chapter 4: Interprocess Communication > Chapter 5: Process Rights Management > > > > For something that is pretty much all about DTrace, take a look also at: > http://www.sun.com/books/catalog/solaris_perf_tools.xml > > Solaris Performance and Tools: Dtrace and MDB techniques for Solaris 10 > and OpenSolaris. > > This book is *great*. It is the companion to Solaris Internals edition > 2. I''ve learned a good bit with this book, highly recommended. > > > As a side note, Jim Mauro, one of the author has just done 3 days up in > Canada: > http://www.exitcertified.com/newsandevents/eventdetails/2007/solaris_roadshow/ > > covering process tools and dtrace and mdb. Apparently this was quite an > impressive session, some linux users in academia and the business world > were impressed enough to want to take a look at Solaris, just because of > dtrace. > > I believe this was the full length version of the presentation that > George Wilson did at Sun Tech Days Atlanta, a real nice presentation > too. I dont have a link for it, but I believe this presentation is > available in open/star office presentation format. Or maybe just in pdf. > Do take a look at that. > > Francois > > >> 2007/2/14, Sean McGrath - Sun Microsystems Ireland >> <sean.mcgrath at sun.com>: >> ???? (Euler Tao) stated: >> < 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. >> >> Dtrace may look ''disordered''. You''re probably finding all the >> dtrace probes points etc that are scattered all over the place >> in various >> modules, libraries etc. The bits that really make up the >> dtrace framework >> are better explained from Bryan''s blog, below. >> >> < >> < I have no experience on reading any Solaris''s Codes yet. >> < Can someone do me a favor? Give me some hints. >> >> Dtrace was the original bit of code that was opened up >> before the full >> opensolaris, way back. Bryan''s blog gives us a tour of the >> dtrace code >> from this initial code: >> >> http://blogs.sun.com/bmc/date/20050125 >> >> Its still good to go through this once in a while. >> >> That along with the dtrace usenix paper gives a good >> overview of how >> dtrace works along with where it lives in opensolaris. >> >> http://www.sun.com/bigadmin/content/dtrace/dtrace_usenix.pdf >> >> That should help you get started :) >> >> Sean. >> . >> < >> < 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 >> < > >> >> < _______________________________________________ >> < dtrace-discuss mailing list >> < dtrace-discuss at opensolaris.org >> >> >> -- >> Sean. >> . >> >> _______________________________________________ >> dtrace-discuss mailing list >> dtrace-discuss at opensolaris.org >> > _______________________________________________ > dtrace-discuss mailing list > dtrace-discuss at opensolaris.org >
On 2/14/07, Jim Mauro <James.Mauro at sun.com> wrote:> For each of the 3 sessions I did in Canada, I came away from each > grinning from > ear-to-ear, recalling my favorite Bryan Cantrill quote - "With DTrace, I > can walk > into a room of hardened technologists and get them giggling".Indeed. I''ve never hated running other OS''s (okay probably with exception of windows) this much before I got to know DTrace. In fact, I now feel totally crippled even in Linux. -- Just me, Wire ...