From: Jan Kiszka <jan.kiszka@web.de>
To: Erik van der Kouwe <vdkouwe@cs.vu.nl>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] [PATCH v2] x86: svm: Always clear event_inj on vmexit
Date: Wed, 02 Jun 2010 08:49:14 +0200 [thread overview]
Message-ID: <4C05FEEA.20909@web.de> (raw)
In-Reply-To: <4C056F16.8000906@cs.vu.nl>
[-- Attachment #1: Type: text/plain, Size: 2349 bytes --]
Erik van der Kouwe wrote:
> Hi,
>
>> We currently only clear SVM_EVTINJ_VALID after successful interrupt
>> delivery. This apparently does not match real hardware which clears the
>> whole event_inj field on every vmexit, including unsuccessful interrupt
>> delivery.
>
> Thanks for the patch. It is a bit hard for me to test right now as I
> messed up my test setup, but I will do so ASAP and let you know.
>
> However, I'm worried that this patch may introduce a new problem (I may
> be mistaken though). There is still this code to load the exit interrupt
> info:
>
> stl_phys(env->vm_vmcb + offsetof(struct vmcb,
> control.exit_int_info_err),
> ldl_phys(env->vm_vmcb + offsetof(struct vmcb,
> control.event_inj_err)));
>
> Now that event_inj is no longer loaded, won't this mean that
> exit_int_info and exit_int_info_err also won't be loaded?
Sorry, can't follow this ATM. But maybe you mean this: there is indeed a
problem with removing the clearance of event_inj.invalid as it may be
later on transferred into exit_int_info. And if we succeed with
injecting the event, that field must not remaind valid.
OK, here is v2:
------->
From: Jan Kiszka <jan.kiszka@siemens.com>
We currently only clear SVM_EVTINJ_VALID after successful interrupt
delivery. This apparently does not match real hardware which clears the
whole event_inj field on every vmexit, including unsuccessful interrupt
delivery.
Reported-by: Erik van der Kouwe <vdkouwe@cs.vu.nl>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
target-i386/op_helper.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/target-i386/op_helper.c b/target-i386/op_helper.c
index dcbdfe7..52e8910 100644
--- a/target-i386/op_helper.c
+++ b/target-i386/op_helper.c
@@ -5388,6 +5388,7 @@ void helper_vmexit(uint32_t exit_code, uint64_t exit_info_1)
ldl_phys(env->vm_vmcb + offsetof(struct vmcb, control.event_inj)));
stl_phys(env->vm_vmcb + offsetof(struct vmcb, control.exit_int_info_err),
ldl_phys(env->vm_vmcb + offsetof(struct vmcb, control.event_inj_err)));
+ stl_phys(env->vm_vmcb + offsetof(struct vmcb, control.event_inj), 0);
env->hflags2 &= ~HF2_GIF_MASK;
/* FIXME: Resets the current ASID register to zero (host ASID). */
--
1.6.0.2
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-06-02 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 17:47 [Qemu-devel] [PATCH] x86: svm: Always clear event_inj on vmexit Jan Kiszka
2010-06-01 20:35 ` [Qemu-devel] " Erik van der Kouwe
2010-06-02 6:49 ` Jan Kiszka [this message]
2010-06-02 7:19 ` [Qemu-devel] [PATCH v2] " Erik van der Kouwe
2010-06-30 19:00 ` Aurelien Jarno
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=4C05FEEA.20909@web.de \
--to=jan.kiszka@web.de \
--cc=gleb@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=qemu-devel@nongnu.org \
--cc=vdkouwe@cs.vu.nl \
/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;
as well as URLs for NNTP newsgroup(s).