From: Rob Landley <landley@trommello.org>
To: "Richard J Moore" <richardj_moore@uk.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: dynamic probes vs kprobes
Date: Tue, 22 Oct 2002 14:38:11 -0500 [thread overview]
Message-ID: <200210221438.11967.landley@trommello.org> (raw)
In-Reply-To: <OF2BA226A6.4D51ABFF-ON80256C5A.004810FC@portsmouth.uk.ibm.com>
On Tuesday 22 October 2002 08:13, Richard J Moore wrote:
> Rob, are you happy with the distinction between dprobes and kprobes?
I'm just trying to understand the distinction. The 2.5 status list had
dprobes in the "ready" state, and my list started from there.
> We are
> not proposing dprobes for 2.5 but rather kprobes + as many of the
> incremental patches that Vamsi posted earlier. Altogether these amount to
> the same thing as dprobes. All of these patches will be available from our
> website.
>
> If on the other hand, if Linus wishes to integrate dprobes then we shan't
> be disappointed :-)
So this is a two-level thing, with a baseline merge level that's independently
useful, plus a full functionality merge that's dependent on the baseline?
I'll try to clarify in my list then.
Could you send me a URL to the separate patches? Right now, the page I have
has a download link for a tarball:
http://www-124.ibm.com/developerworks/opensource/linux/projects/dprobes/releases/dprobes-v3.6.3.tar.gz
If I understand the relationship between kprobes and dprobes correctly, it
would be nice to have a standalone kprobes patch URL, and a second "dprobes
on top of that" URL.
> Richard
> RAS Project Lead - IBM Linux Technology Centre
Rob
--
http://penguicon.sf.net - Terry Pratchett, Eric Raymond, Pete Abrams, Illiad,
CmdrTaco, liquid nitrogen ice cream, and caffienated jello. Well why not?
prev parent reply other threads:[~2002-10-23 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 13:13 Richard J Moore
2002-10-22 19:38 ` Rob Landley [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=200210221438.11967.landley@trommello.org \
--to=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richardj_moore@uk.ibm.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
all inboxes | Powered by JetHome®