From: "Jan Beulich" <JBeulich@novell.com>
To: "Arjan Ven" <arjan@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] double fault enhancements
Date: Mon, 30 Jan 2006 11:12:23 +0100 [thread overview]
Message-ID: <43DDF497.76F0.0078.0@novell.com> (raw)
In-Reply-To: <1138615114.2977.19.camel@laptopd505.fenrus.org>
>I would hope TSS and such remain in the kernel static space, because
>those are the kind of things I'd like to be read only over time...
I'm not sure what you're trying to say. A TSS can't possibly be read-only, as the processor will need to write to it
any time it gets used.
>Also the last chunk of your patch has nothing to do with what you
>describe here... and seems sort of suprious. (it might be a useful
>cleanup, but it should be independent)
It is relevant, for the preprocessor pseudo-assertion in cpu_init() to work. Anyway, I submitted the THREAD_ORDER
introduction as a separate cleanup-like (as you suggest) patch before, without getting any positive or negative
responses back...
Jan
next prev parent reply other threads:[~2006-01-30 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-01-30 10:08 ` (correction) " Jan Beulich
[not found] <43DDF050.76F0.0078.0@novell.com.suse.lists.linux.kernel>
2006-01-31 12:35 ` Andi Kleen
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=43DDF497.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=arjan@infradead.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