From: Richard J Moore <richardj_moore@uk.ibm.com>
To: prasanna@in.ibm.com
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Hien Q Nguyen <nguyhien@us.ibm.com>,
systemtap@sources.redhat.com
Subject: Re: [...] kprobes [minutes] portion 20060406
Date: Fri, 07 Apr 2006 08:43:00 -0000 [thread overview]
Message-ID: <OFA800EA33.3E239069-ON41257149.002FC3D2-41257149.002FE3DC@uk.ibm.com> (raw)
In-Reply-To: <20060407082517.GA7546@in.ibm.com>
systemtap-owner@sourceware.org wrote on 07/04/2006 09:25:17:
>
> On Thu, Apr 06, 2006 at 05:28:38PM -0400, Frank Ch. Eigler wrote:
> > Hi -
> >
> > On Thu, Apr 06, 2006 at 02:14:46PM -0700, Hien Q Nguyen wrote:
> > > User space probe
> > > Prasanna had prototype that execute the handler in the user space
[...]
> >
> > Beyond merely dispatching, it is important to consider what such a
> > handler can do. Would it still be useful if it cannot call into the
> > kernel-side runtime, if it cannot share variables with kernel-space
> > probes?
>
> No. The purpose of prototype was to see how it can be implemented.
> To my opinion having handler run in user-space does not suit well for
> system-wide tracing. But that might be one of the alternative approaches
> to per-process tracing, since ptrace is found to have more performance
> related problems.
>
>
Agreed, but don't let the creation of per-process probe handlers detract
from the argument for a system-wide capabiltiy; that's the real
battle-ground.
Richard
> Thanks
> Prasanna
> --
> Thanks & Regards
> Prasanna S Panchamukhi
> Linux Technology Center
> India Software Labs, IBM Bangalore
> Email: prasanna@in.ibm.com
> Ph: 91-80-51776329
prev parent reply other threads:[~2006-04-07 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF450EB249.F3B0B23E-ON88257148.00738621-88257148.0074730E@us.ibm.com>
2006-04-06 21:28 ` Frank Ch. Eigler
2006-04-06 22:08 ` Richard J Moore
2006-04-07 8:25 ` Prasanna S Panchamukhi
2006-04-07 8:43 ` Richard J Moore [this message]
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=OFA800EA33.3E239069-ON41257149.002FC3D2-41257149.002FE3DC@uk.ibm.com \
--to=richardj_moore@uk.ibm.com \
--cc=fche@redhat.com \
--cc=nguyhien@us.ibm.com \
--cc=prasanna@in.ibm.com \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).