From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Alexander Graf <agraf@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH] x86, nmi: workaround sti; hlt race vs nmi; intr
Date: Tue, 28 Sep 2010 18:30:24 +0200 [thread overview]
Message-ID: <4CA21820.5010704@redhat.com> (raw)
In-Reply-To: <4CA20B21.7060809@zytor.com>
On 09/28/2010 05:34 PM, H. Peter Anvin wrote:
> On 09/28/2010 01:50 AM, Avi Kivity wrote:
> >
> > Personally I think the safer route is to take the patch. There are
> > other processors besides Intel and AMD and we can't test all of them,
> > not to mention various emulators and virtual machine monitors out there.
> >
>
> Speaking for the smoltering crater that used to be *Transmeta*, I'm
> (from memory) quite certain they blocked NMI and that this was
> intentional behavior.
>
We'll need:
- Intel
- AMD
- Geode
- Via
- kvm (currently no, but plan to)
- qemu
- vmware
- others?
It should be relatively simple to write a small test case to test this.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-28 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 16:28 [PATCH] x86, nmi: workaround sti; hlt race vs nmi; intr Avi Kivity
2010-09-27 8:38 ` Avi Kivity
2010-09-27 9:13 ` Alexander Graf
2010-09-27 9:15 ` Alexander Graf
2010-09-27 9:17 ` Avi Kivity
2010-09-27 9:22 ` Alexander Graf
2010-09-27 9:27 ` Avi Kivity
2010-09-27 9:36 ` Alexander Graf
2010-09-27 21:55 ` H. Peter Anvin
2010-09-28 8:50 ` Avi Kivity
2010-09-28 9:22 ` Roedel, Joerg
2010-09-28 15:34 ` H. Peter Anvin
2010-09-28 16:30 ` Avi Kivity [this message]
2010-09-27 10:31 ` Joerg Roedel
2010-09-27 14:17 ` Avi Kivity
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=4CA21820.5010704@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=hpa@zytor.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.