From: Theodore Tso <tytso@mit.edu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
systemtap@sourceware.org
Subject: Re: [RFC] fix kallsyms to allow discrimination of local symbols
Date: Wed, 23 Jul 2008 13:47:53 -0400 [thread overview]
Message-ID: <20080723174753.GL8826@mit.edu> (raw)
In-Reply-To: <1216831226.13159.26.camel@localhost.localdomain>
On Wed, Jul 23, 2008 at 12:40:26PM -0400, James Bottomley wrote:
> I'm not sure we'd want to do it with CTF either ... the only reason to
> have it in the kernel is if the kernel wants to use it. Right at the
> moment with the dwarf, systemtap userspace is the only consumer, so it
> doesn't need to be in the kernel; I don't really see that changing with
> CTF. I think dtrace does it because the D runtime is in-kernel so some
> of the run time typing needs the CTF.
As far as I understand things, all of that is done in userspace and
byte-compiled down to run in their simple DTrace VM. The reason for
CTF being in the Open Slaris is for their kernel debugger (kmdb) and
so that a crash dump can be guaranteed to be easily analyzed.[1]
- Ted
[1] http://blogs.sun.com/levon/entry/reducing_ctf_overhead
next prev parent reply other threads:[~2008-07-23 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 21:43 [RFC] fix kallsyms to allow discrimination of local symbols James Bottomley
2008-07-22 1:44 ` Frank Ch. Eigler
2008-07-22 3:53 ` James Bottomley
2008-07-22 11:51 ` Frank Ch. Eigler
2008-07-22 15:14 ` James Bottomley
2008-07-22 16:05 ` Frank Ch. Eigler
2008-07-23 1:48 ` Theodore Tso
2008-07-23 4:16 ` Frank Ch. Eigler
2008-07-23 16:25 ` Theodore Tso
2008-07-23 16:40 ` James Bottomley
2008-07-23 17:47 ` Theodore Tso [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-24 16:03 Frank Ch. Eigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080723174753.GL8826@mit.edu \
--to=tytso@mit.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox