[<prev] [next>] [day] [month] [year] [list]
Message-ID: <46088E59.6030304@hitachi.com>
Date: Tue, 27 Mar 2007 12:24:09 +0900
From: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
To: "Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>
Cc: hch@...radead.org, Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Prasanna S Panchamukhi <prasanna@...ibm.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
SystemTAP <systemtap@...rces.redhat.com>,
Satoshi Oshima <soshima@...hat.com>,
Hideo Aoki <haoki@...hat.com>,
Yumiko Sugita <yumiko.sugita.yf@...achi.com>,
"Frank Ch. Eigler" <fche@...hat.com>
Subject: Re: [RFC][Patch 1/4] kprobe fast unregistration
Hi Anil,
Keshavamurthy, Anil S wrote:
> On Mon, Mar 26, 2007 at 12:17:49PM +0900, Masami Hiramatsu wrote:
>> Hi Christoph and Anil,
>>
>> Thank you for your comments.
>>
>> Christoph Hellwig wrote:
>>> Speeding up the unregistration is a very good idea, but this interface
>>> is rather horrible. It's almost a receipe for users to get it wrong.
>> Keshavamurthy, Anil S wrote:
>>> I agree with Christop that the interface is horrible and error prone.
>> OK, I agree. I had chosen a confusable name.
> Keep in mind that the the sequence of unregistering a
> probe should be same irrespecitve of whether user wants
> to unregister a single probe or user want to
> unregister more that one probe, i.e. you can not say
> use this call (unregister_kprobe() ) for unregistering
> a probe which is b.t.w slow and use this set of calls if you
> have more than one kprobes to unregister for faster unregistration.
Would you mean that we should integrate unregistration interface?
Or, would you mean that you prefer "disable_kprobe()" since that
name provides another meaning?
Thanks,
--
Masami HIRAMATSU
Linux Technology Center
Hitachi, Ltd., Systems Development Laboratory
E-mail: masami.hiramatsu.pt@...achi.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists