From: Erik van der Kouwe <vdkouwe@cs.vu.nl>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] x86: svm: Always clear event_inj on vmexit
Date: Tue, 01 Jun 2010 22:35:34 +0200 [thread overview]
Message-ID: <4C056F16.8000906@cs.vu.nl> (raw)
In-Reply-To: <4C05479E.3010705@siemens.com>
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?
With kind regards,
Erik
Jan Kiszka wrote:
> 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>
> ---
>
> (before it gets lost)
> Erik, please confirm that this works for you.
>
> target-i386/op_helper.c | 8 +-------
> 1 files changed, 1 insertions(+), 7 deletions(-)
>
> diff --git a/target-i386/op_helper.c b/target-i386/op_helper.c
> index dcbdfe7..caabdb4 100644
> --- a/target-i386/op_helper.c
> +++ b/target-i386/op_helper.c
> @@ -1263,13 +1263,6 @@ void do_interrupt(int intno, int is_int, int error_code,
> #endif
> do_interrupt_real(intno, is_int, error_code, next_eip);
> }
> -
> -#if !defined(CONFIG_USER_ONLY)
> - if (env->hflags & HF_SVMI_MASK) {
> - uint32_t event_inj = ldl_phys(env->vm_vmcb + offsetof(struct vmcb, control.event_inj));
> - stl_phys(env->vm_vmcb + offsetof(struct vmcb, control.event_inj), event_inj & ~SVM_EVTINJ_VALID);
> - }
> -#endif
> }
>
> /* This should come from sysemu.h - if we could include it here... */
> @@ -5388,6 +5381,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). */
next prev parent reply other threads:[~2010-06-01 20:35 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 ` Erik van der Kouwe [this message]
2010-06-02 6:49 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2010-06-02 7:19 ` 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=4C056F16.8000906@cs.vu.nl \
--to=vdkouwe@cs.vu.nl \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=joerg.roedel@amd.com \
--cc=qemu-devel@nongnu.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.