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:
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? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/