From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Glauber Costa <glommer@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disable interrupt shadow state for emulated instruction
Date: Thu, 09 Apr 2009 10:41:47 +0300 [thread overview]
Message-ID: <49DDA6BB.6080909@redhat.com> (raw)
In-Reply-To: <49DCED9A.8030108@zytor.com>
H. Peter Anvin wrote:
> Glauber Costa wrote:
>> mov ss is a non-issue, since it is executed natively.
>
> In real mode?
>
Yes.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-04-09 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 17:57 [PATCH] disable interrupt shadow state for emulated instruction Glauber Costa
2009-04-08 18:16 ` H. Peter Anvin
2009-04-08 18:31 ` Glauber Costa
2009-04-08 18:31 ` H. Peter Anvin
2009-04-08 18:43 ` Glauber Costa
2009-04-08 19:45 ` Gleb Natapov
2009-04-09 7:41 ` Avi Kivity [this message]
2009-04-09 7:41 ` Avi Kivity
2009-04-09 7:39 ` Avi Kivity
2009-04-08 19:48 ` Gleb Natapov
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=49DDA6BB.6080909@redhat.com \
--to=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.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