public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: Keshavamurthy Anil S <anil.s.keshavamurthy@intel.com>
Cc: Anderw Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>, Dean Nelson <dcn@sgi.com>,
	Tony Luck <tony.luck@intel.com>,
	Anath Mavinakayanahalli <ananth@in.ibm.com>,
	Prasanna Panchamukhi <prasanna@in.ibm.com>,
	Dave M <davem@davemloft.net>, Andi Kleen <ak@suse.de>
Subject: Re: [(take 2)patch 6/7] Kprobes registers for notify page fault
Date: Fri, 21 Apr 2006 10:53:29 +1000	[thread overview]
Message-ID: <19743.1145580809@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Thu, 20 Apr 2006 17:38:47 MST." <20060420173846.B12536@unix-os.sc.intel.com>

Keshavamurthy Anil S (on Thu, 20 Apr 2006 17:38:47 -0700) wrote:
>On Fri, Apr 21, 2006 at 10:14:04AM +1000, Keith Owens wrote:
>> Anil S Keshavamurthy (on Thu, 20 Apr 2006 16:25:02 -0700) wrote:
>> >---
>> >@@ -654,6 +659,9 @@ static int __init init_kprobes(void)
>> > 	if (!err)
>> > 		err = register_die_notifier(&kprobe_exceptions_nb);
>> > 
>> >+	if (!err)
>> >+		err = register_page_fault_notifier(&kprobe_page_fault_nb);
>> >+
>> > 	return err;
>> > }
>> > 
>> 
>> The rest of the patches look OK, but this one does not.  init_kprobes()
>> registers the main kprobe exception handler, not the page fault
>> handler.
>I am registering for register_page_fault_notifier() and as you can see
>I am not deleting the old register_die_notifier() which is also required
>for getting notified on int3/break and single-step traps. 
>So no issues here.

Patch 7 conditionally registers a page fault handler, plus an
unregister when there are no user space probes.  Why does patch 6
unconditionally register a page fault handler?


  reply	other threads:[~2006-04-21  0:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 23:24 [(take 2)patch 0/7] Notify page fault call chain Anil S Keshavamurthy
2006-04-20 23:24 ` [(take 2)patch 1/7] Notify page fault call chain for x86_64 Anil S Keshavamurthy
2006-04-20 23:24 ` [(take 2)patch 2/7] Notify page fault call chain for i386 Anil S Keshavamurthy
2006-04-20 23:24 ` [(take 2)patch 3/7] Notify page fault call chain for ia64 Anil S Keshavamurthy
2006-04-20 23:25 ` [(take 2)patch 4/7] Notify page fault call chain for powerpc Anil S Keshavamurthy
2006-04-20 23:25 ` [(take 2)patch 5/7] Notify page fault call chain for sparc64 Anil S Keshavamurthy
2006-04-20 23:25 ` [(take 2)patch 6/7] Kprobes registers for notify page fault Anil S Keshavamurthy
2006-04-21  0:07   ` Keshavamurthy Anil S
2006-04-21  0:14   ` Keith Owens
2006-04-21  0:38     ` Keshavamurthy Anil S
2006-04-21  0:53       ` Keith Owens [this message]
2006-04-21  1:03         ` Keshavamurthy Anil S
2006-04-20 23:25 ` [(take 2)patch 7/7] Notify page fault call chain Anil S Keshavamurthy
2006-04-24  9:19   ` bibo mao
2006-04-25  1:10     ` Keith Owens
2006-04-25  5:43       ` Keshavamurthy Anil S
2006-04-24 19:28 ` [(take 2)patch 0/7] " Robin Holt
2006-04-25  6:01   ` Keshavamurthy Anil S
2006-04-25 10:15     ` Robin Holt

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=19743.1145580809@ocs3.ocs.com.au \
    --to=kaos@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=dcn@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prasanna@in.ibm.com \
    --cc=tony.luck@intel.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