From: Erik van der Kouwe <vdkouwe@cs.vu.nl>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
qemu-devel <qemu-devel@nongnu.org>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] x86: svm: Always clear event_inj on vmexit
Date: Wed, 02 Jun 2010 09:19:02 +0200 [thread overview]
Message-ID: <4C0605E6.1080602@cs.vu.nl> (raw)
In-Reply-To: <4C05FEEA.20909@web.de>
Hi,
> 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.
Correct.
> OK, here is v2:
I tested this and AFAICS this one works fine and fixes the problem.
Thanks,
Erik
next prev parent reply other threads:[~2010-06-02 7:19 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 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
2010-06-02 7:19 ` Erik van der Kouwe [this message]
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=4C0605E6.1080602@cs.vu.nl \
--to=vdkouwe@cs.vu.nl \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--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 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).