[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <47849E00.76E4.0078.0@novell.com>
Date: Wed, 09 Jan 2008 09:12:16 +0000
From: "Jan Beulich" <jbeulich@...ell.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: <mingo@...e.hu>, <pq@....fi>, <torvalds@...ux-foundation.org>,
"Dave Airlie" <airlied@...ux.ie>, <hch@....de>, <ak@...e.de>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Revert "x86: optimize page faults like all other
achitectures and kill notifier cruft"
>That change has been in the mainline tree for nearly three months. All
>these affected parties have left it until the eve of 2.6.24 to actually
>tell us about it. This is causing me sympathy problems :(
Not true - I complained about this on Dec 3rd (attached), with the result of
not getting a response from anyone but Andi (agreeing to restore these
notifiers).
Jan
Date: Mon, 03 Dec 2007 13:31:07 +0000
From: "Jan Beulich" <jbeulich@...ell.com>
To: <akpm@...ux-foundation.org>,<torvalds@...ux-foundation.org>,
<hch@....de>
Cc: <ananth@...ibm.com>,<prasanna@...ibm.com>,
<anil.s.keshavamurthy@...el.com>, <ak@...e.de>,
<linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: x86: optimize page faults like all other achitectures and
kill notifier cruft
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Ever since I started to try to get at least some fundamental infrastructure=
pieces merged for using NLKD on Linux I was told that direct calls out of
exception handlers for the sake of an individual (and perhaps even small)
sub-system is undesirable.
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: Instead of adding direct calls to x86, all the
other architectures should have followed the notifier model in order for
the infrastructure to be usable by external components, especially if
these aren't allowed into the kernel.
Am I to conclude that replacing direct calls elsewhere in the tree (in =
order
to e.g. avoid all kinds of small sub-components leaving their footprint in
core files like kernel/fork.c) is no longer a desirable goal, thereby =
making
it almost impossible to ever host a kernel debugger *without* having to
patch core files.
Thanks, Jan
Powered by blists - more mailing lists