From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
hch@lst.de, ananth@in.ibm.com, prasanna@in.ibm.com,
anil.s.keshavamurthy@intel.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: x86: optimize page faults like all other achitectures and kill notifier cruft
Date: Mon, 3 Dec 2007 19:38:07 +0100 [thread overview]
Message-ID: <200712031938.08036.ak@suse.de> (raw)
In-Reply-To: <4754132B.76E4.0078.0@novell.com>
On Monday 03 December 2007 14:31, Jan Beulich wrote:
> Making the exception notifiers report the right (correct) information (and,
> specific to x86, ensuring they get called in the right place) was one of
> the fundamental things, and just now I see that this is being reverted for
> (in my eyes) no good reason:
FWIW I agree it would be better to put the notifiers back.
-Andi
prev parent reply other threads:[~2007-12-03 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 13:31 x86: optimize page faults like all other achitectures and kill notifier cruft Jan Beulich
2007-12-03 18:38 ` Andi Kleen [this message]
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=200712031938.08036.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=hch@lst.de \
--cc=jbeulich@novell.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
--cc=torvalds@linux-foundation.org \
/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