Re: [2/3 PATCH] Kprobes: User space probes support- readpage hooks

From: Richard J Moore
Date: Tue Mar 21 2006 - 11:18:31 EST


Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote on 21/03/2006 12:15:50:

> > I think you'll find it happened the other way round. Sun openly
> > my white papers. They even stole the name of an ancestor to kprobes.
> > who cares, it not relevant or particularly interesting whether the
> > or the egg came first.
> I know your papers, too. In fact dprobes' RPN program downloads are a
> better design than systemtap's generation of kernel code. it's a pity
> you gave up on dprobes instead of applying the required work to it and
> integrate it with other bits of a tracing framework.

Fascinating, gave up on dprobes, not really! I thought the kernel community
felt it was the wrong implementation. We did remove all the RPN stuff to a
loadable kernel module and left behind a minimal API set - krpobes - which
comprised the kernel probing mechanism, user-space probes extensions and
watchpoint probes extension. The result was identical functionality to the
original dprobes but with a minimal patch to the mainline kernel. But in
addition it provided a very much more generalized interface that would
allow other utilities to exploit the kernel interface, which they have. In
this sense dprobes still exists and can be used on top of krpobes. What
would you recommend be retained from dprobes? And what further

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at