From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] double fault enhancements
Date: 31 Jan 2006 13:35:29 +0100 [thread overview]
Message-ID: <p73d5i8mv72.fsf@verdi.suse.de> (raw)
In-Reply-To: <43DDF050.76F0.0078.0@novell.com.suse.lists.linux.kernel>
"Jan Beulich" <JBeulich@novell.com> writes:
> From: Jan Beulich <jbeulich@novell.com>
>
> Make the double fault handler use CPU-specific stacks. Add some
> abstraction to simplify future change of other exception handlers to go
> through task gates. Change the pointer validity checks in the double
> fault handler to account for the fact that both GDT and TSS aren't in
> static kernel space anymore. Add a new notification of the event
> through the die notifier chain, also providing some environmental
> adjustments so that various infrastructural things work independent of
> the fact that the fault and the callbacks are running on other then the
> normal kernel stack.
Looks good to me. Feel free to include a Acked-by: ak@suse.de
in future versions.
-Andi
next parent reply other threads:[~2006-01-31 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43DDF050.76F0.0078.0@novell.com.suse.lists.linux.kernel>
2006-01-31 12:35 ` Andi Kleen [this message]
2006-01-30 9:54 [PATCH] double fault enhancements Jan Beulich
2006-01-30 9:58 ` Arjan van de Ven
2006-01-30 10:12 ` Jan Beulich
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=p73d5i8mv72.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=linux-kernel@vger.kernel.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