From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jan Beulich <jbeulich@novell.com>,
the arch/x86 maintainers <x86@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/5] xen/x86-64: clean up warnings aboutIST-using traps
Date: Fri, 08 May 2009 08:31:10 -0700 [thread overview]
Message-ID: <4A04503E.3050807@goop.org> (raw)
In-Reply-To: <20090508085805.GA28455@elte.hu>
Ingo Molnar wrote:
> Yes. Also, patches 1-2-3 really just do the same thing, one fixes
> the other one. Would be nice to have a single patch for that whole
> ugly topic of 64-bit Xen not handling ISTs properly.
>
Well, 1 is sufficient on its own to fix the breakpoint/watchpoint
problem. Looks like I need to do something similar with stack. The 2,3
are more general cleanups that aren't essential to the functional fix,
and should definitely be folded together.
> If this was a CPU we'd say "sorry, dont run Linux on it then" ...
>
?? Guests don't really need IST because all the tricky traps that
really require it (NMI, MCE, etc) are handled by Xen. The stack
exception was an oversight on my part, because I thought it was
something that would only happen with a bad kernel stack (but I guess
that's doublefault).
> I've applied the reservation fix to x86/urgent, and the #5 patch to
> x86/xen (it's more of a cleanup, not a fix for .30, right?).
>
Right.
J
next prev parent reply other threads:[~2009-05-08 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 18:56 [PATCH 2/5] xen/x86-64: clean up warnings about IST-using traps Jeremy Fitzhardinge
2009-05-08 7:20 ` [Xen-devel] [PATCH 2/5] xen/x86-64: clean up warnings aboutIST-using traps Jan Beulich
2009-05-08 8:58 ` Ingo Molnar
2009-05-08 15:31 ` Jeremy Fitzhardinge [this message]
2009-05-08 15:23 ` Jeremy Fitzhardinge
2009-05-08 15:30 ` [Xen-devel] [PATCH 2/5] xen/x86-64: clean up warnings aboutIST-usingtraps 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=4A04503E.3050807@goop.org \
--to=jeremy@goop.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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