From: Christoph Hellwig <hch@infradead.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 double fault enhancements
Date: Fri, 24 Feb 2006 18:49:41 +0000 [thread overview]
Message-ID: <20060224184940.GA5816@infradead.org> (raw)
In-Reply-To: <43FDADA0.76F0.0078.0@novell.com>
On Thu, Feb 23, 2006 at 12:42:08PM +0100, Jan Beulich wrote:
> >Can't we use CONFIG_DOUBLEFAULT throughout? It's very much clearer.
>
> We could, when not considering broader use. I specifically introduced N_EXCEPTION_TSS
> so that it wouldn't be as hard as it currently is to have other exceptions got through task
> gates (nlkd's fault/trap/abort infrastructure does, for example).
So please keep this in your out of tree patch. In mainline it's just
needlessly obsfucating the code.
next prev parent reply other threads:[~2006-02-24 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 10:59 [PATCH] i386 double fault enhancements Jan Beulich
2006-02-22 22:32 ` Andrew Morton
2006-02-23 10:34 ` Andi Kleen
2006-02-23 11:42 ` Jan Beulich
2006-02-24 18:49 ` Christoph Hellwig [this message]
2006-03-03 9:30 ` 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=20060224184940.GA5816@infradead.org \
--to=hch@infradead.org \
--cc=JBeulich@novell.com \
--cc=akpm@osdl.org \
--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