linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Rusty Lynch <rusty@linux.intel.com>
Cc: Christoph Lameter <clameter@engr.sgi.com>,
	Rusty Lynch <rusty.lynch@intel.com>,
	linux-mm@kvack.org, prasanna@in.ibm.com,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	anil.s.keshavamurthy@intel.com
Subject: Re: [PATCH] Only process_die notifier in ia64_do_page_fault if KPROBES is configured.
Date: Tue, 30 Aug 2005 03:08:44 +0200	[thread overview]
Message-ID: <200508300308.44706.ak@suse.de> (raw)
In-Reply-To: <20050830001905.GA18279@linux.jf.intel.com>

On Tuesday 30 August 2005 02:19, Rusty Lynch wrote:

>
> So, assuming inlining the notifier_call_chain would address Christoph's
> conserns, is the following patch something like what you are sugesting?

Yes.

Well in theory you could make fast and slow notify_die too, but that's
probably not worth it.

-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-08-30  1:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26 22:46 Rusty Lynch
2005-08-26 23:05 ` Christoph Lameter
2005-08-27  0:24   ` [PATCH] " Andi Kleen
2005-08-30  0:19     ` Rusty Lynch
2005-08-30  1:08       ` Andi Kleen [this message]
2005-08-30  3:28       ` Christoph Lameter
2005-08-30 11:18       ` Matthew Wilcox
2005-09-19 18:22         ` Christoph Lameter
  -- strict thread matches above, loose matches on Subject: below --
2005-08-30 23:05 Luck, Tony
2005-08-30 23:38 ` Andi Kleen
2005-08-30 23:54   ` Christoph Lameter
2005-08-31  0:05     ` Andi Kleen
2005-08-25 20:14 Christoph Lameter

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=200508300308.44706.ak@suse.de \
    --to=ak@suse.de \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=clameter@engr.sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=prasanna@in.ibm.com \
    --cc=rusty.lynch@intel.com \
    --cc=rusty@linux.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