public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vamsi Krishna S ." <vamsi@in.ibm.com>
To: Skip Ford <skip.ford@verizon.net>
Cc: Rob Landley <landley@trommello.org>,
	linux-kernel@vger.kernel.org, boissiere@adiglobal.com
Subject: Re: Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list.
Date: Mon, 28 Oct 2002 16:05:55 +0530	[thread overview]
Message-ID: <20021028160555.A7580@in.ibm.com> (raw)
In-Reply-To: <200210280955.g9S9tqi3002027@pool-141-150-241-241.delv.east.verizon.net>; from skip.ford@verizon.net on Mon, Oct 28, 2002 at 04:55:45AM -0500

Hi Skip,

On Mon, Oct 28, 2002 at 04:55:45AM -0500, Skip Ford wrote:
> 
> The first paragraph seems to say that only the base patch is being
> submitted and the watchpoint and user-space extensions can be
> retrieved from the site.
> 
That is not the intention, I will reword that first paragraph on the
website to clarify this.

> But then it goes on to say that you are proposing those for inclusion
> also.  I'm confused and I've been using your patches.  Also, that first
> paragraph mentions "add-on" patches while all along I thought your
> intention was to have enough of dprobes in the kernel so that patching
> wasn't necessary.
> 
Yes, our intention is to have enough of infrastructure in the kernel
to do something like dprobes as an external module without
patching the kernel. 

dprobes provides kernel / user space probes and kernel space 
watchpoints along with an RPN interpreter and communication with
the user space in the form a char device. Now, here is what
various bits of kprobes patches do:

1. kprobes - base patch
   Enables implementing a part of dprobes (kernel space probes)
   without further patching the kernel.

2. debug register management patch
3. kwatch points patch
   Enables implementing another part of dprobes (kernel space 
   watchpoints) without further patching the kernel.

4. user space probes patch
   Enables implementing another part of dprobes (user space 
   probes) without further patching the kernel.

Another point to note is that kprobes should be seen as an independent
facility, a sort of infrastructure on top of which more comprehensive
tools such as dprobes could be built. kprobes infrastructure could
potentially be used in other tools such as kdb/kgdb too.

We would like all four patches to be in the kernel. However, the base
patch has been on the list for a few months, has been looked at and
commented upon by other kernel developers including Rusty and Linus. 
So, we strongly hope for its inclusion. Once kprobes is in, other
patches (notably the user space probes patch) could be considered
a straight forward enhancement to kprobes and may be included
even after the freeze. OTOH if Linus agrees to include all four
patches, that will be great :-)

Thanks for your comments, hope this clarifies the issues.

-- 
Vamsi Krishna S.
Linux Technology Center,
IBM Software Lab, Bangalore.
Ph: +91 80 5044959
Internet: vamsi@in.ibm.com

  reply	other threads:[~2002-10-28 10:16 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-28  2:17 Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Rob Landley
2002-10-28  8:25 ` Vamsi Krishna S .
2002-10-28  9:55   ` Skip Ford
2002-10-28 10:35     ` Vamsi Krishna S . [this message]
2002-10-28 10:29 ` Andrew Walrond
2002-10-28 10:40   ` Rob Landley
2002-10-28 12:15   ` Nicholas Wourms
2002-10-28 13:31   ` Dave Jones
2002-10-28 14:05     ` Andrew Walrond
2002-10-28 14:42       ` Andrew Walrond
2002-10-28 15:02       ` Alan Cox
2002-10-30  7:29 ` Dave Cinege
2002-10-30  7:40   ` Jeff Garzik
2002-10-30  8:22     ` Dave Cinege
2002-10-30  8:37       ` Russell King
2002-10-30  9:32         ` Dave Cinege
2002-10-30  8:41       ` Jeff Garzik
2002-10-30  8:51       ` Erik Andersen
2002-10-30  9:00         ` Miles Bader
2002-10-30  9:06           ` Jeff Garzik
2002-10-30  9:19             ` Miles Bader
2002-10-30  9:26               ` Jeff Garzik
2002-10-30  9:38                 ` Miles Bader
2002-10-30  9:42                   ` Erik Andersen
2002-10-30 10:50                   ` Jeff Garzik
2002-10-30  9:34             ` Russell King
2002-10-30 10:07               ` Dave Cinege
2002-10-30  9:36             ` Erik Andersen
2002-10-30 10:52               ` Jeff Garzik
2002-10-30  9:55           ` Dave Cinege
2002-10-30  9:59             ` Miles Bader
2002-10-30 10:24               ` Dave Cinege
2002-10-30 10:05             ` Jeff Garzik
2002-10-30 10:14               ` Dave Cinege
2002-10-30 10:24                 ` Jeff Garzik
2002-10-30 10:42                   ` Dave Cinege
2002-10-30 11:06                     ` Jeff Garzik
2002-10-30  9:55         ` Dave Cinege
2002-10-30 10:29           ` Jeff Garzik
2002-11-04  2:13           ` Rob Landley
2002-11-04  7:39             ` Help needed with IRQ on Ali chipset Jacek Pliszka
2002-11-04 13:10             ` Abbott and Costello meet Crunch Time -- Penultimate 2.5 merge candidate list Alan Cox
2002-11-04 22:52             ` Werner Almesberger
2002-11-04 23:02               ` Jeff Garzik
2002-11-04 18:16                 ` Rob Landley
2002-11-04 23:22                 ` Werner Almesberger
2002-10-30 14:32       ` Alan Cox

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=20021028160555.A7580@in.ibm.com \
    --to=vamsi@in.ibm.com \
    --cc=boissiere@adiglobal.com \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skip.ford@verizon.net \
    /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