From: Avi Kivity <avi@qumranet.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, kvm-devel <kvm@vger.kernel.org>,
Mohammed Gamal <m.gamal005@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH 2/2] VMX: Reinject real mode exception
Date: Mon, 14 Jul 2008 13:04:17 +0300 [thread overview]
Message-ID: <487B24A1.3090309@qumranet.com> (raw)
In-Reply-To: <0B53E02A2965CE4F9ADB38B34501A3A10653F536@orsmsx505.amr.corp.intel.com>
Nakajima, Jun wrote:
> On 7/13/2008 8:31:44 AM, Avi Kivity wrote:
>
>> Avi Kivity wrote:
>>
>>> Well, xen and bochs do not push an error code for real mode #GP. I
>>> tried running the attached test program but it doesn't work on real
>>> hardware (it does work on bochs).
>>>
>>>
>> Jun, perhaps you can clarify? do #GP exceptions in real-mode push an
>> error code?
>>
>
> Avi,
>
> Exceptions in real-mode do not push an error code in the stack.
Thanks. You might consider updating the documentation, for example #DF
states that an error code of 0 is always pushed.
> In vm86 mode #GP exceptions push an error code, triggering a protected-mode handler in the monitor, as you know. Is it possible that the guest is actually using vm86 mode?
>
No, it's a real mode guest. It's emulated using vm86, of course, but it
thinks it's in real mode. The question was, when we inject a #GP, #SS,
or #DF exception, should we also inject an error code, and according to
your clarification, the answer is no.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-07-14 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 11:40 [PATCH 2/2] VMX: Reinject real mode exception Jan Kiszka
2008-07-13 12:06 ` Avi Kivity
2008-07-13 12:27 ` Jan Kiszka
2008-07-13 15:28 ` Avi Kivity
2008-07-13 15:31 ` Avi Kivity
2008-07-13 18:47 ` Nakajima, Jun
2008-07-13 19:22 ` Mohammed Gamal
2008-07-14 10:04 ` Avi Kivity [this message]
2008-07-14 10:28 ` Jan Kiszka
2008-07-14 11:30 ` Avi Kivity
2008-07-14 16:00 ` Nakajima, Jun
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=487B24A1.3090309@qumranet.com \
--to=avi@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@web.de \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--cc=riel@surriel.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