From: Paolo Bonzini <pbonzini@redhat.com>
To: Peng Hao <peng.hao2@zte.com.cn>,
rth@twiddle.net, ehabkost@redhat.com, kvm@vger.kernel.org,
mtosatti@redhat.com
Cc: qemu-devel@nongnu.org, "J. Kiszka" <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH] target-i386:kvm_get/put_vcpu_events don't handle sipi_vector
Date: Wed, 12 Jul 2017 19:00:26 +0200 [thread overview]
Message-ID: <7cdaad86-333a-4b7b-1c91-09ad6e036ecd@redhat.com> (raw)
In-Reply-To: <1499850727-50728-1-git-send-email-peng.hao2@zte.com.cn>
On 12/07/2017 11:12, Peng Hao wrote:
> qemu call kvm_get_vcpu_events, and kernel return sipi_vector always 0,
> never valid when reporting to user space. But qemu call kvm_put_vcpu_events
> will make sipi_vector in kernel be 0. This will accidently modify sipi_vector
> when sipi_vector in kernel is not 0.
>
> Signed-off-by: Peng Hao <peng.hao2@zte.com.cn>
> Reviewed-by: Wang Yechao <wang.yechao255@zte.com.cn>
> ---
> target/i386/kvm.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index f84a49d..bbbd696 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -2417,7 +2417,6 @@ static int kvm_put_vcpu_events(X86CPU *cpu, int level)
> events.nmi.masked = !!(env->hflags2 & HF2_NMI_MASK);
> events.nmi.pad = 0;
>
> - events.sipi_vector = env->sipi_vector;
> events.flags = 0;
>
> if (has_msr_smbase) {
This should clear KVM_VCPUEVENT_VALID_SIPI_VECTOR in the "if" statement
below. Otherwise, you're passing a random value to the kernel.
> @@ -2506,8 +2505,6 @@ static int kvm_get_vcpu_events(X86CPU *cpu)
> }
> }
>
> - env->sipi_vector = events.sipi_vector;
> -
> return 0;
> }
>
>
I think what you're seeing is a race like this:
VCPU 0 VCPU 1
[qemu] kvm_get_mp_state
[kvm] kvm_apic_accept_events
__apic_accept_irq
set KVM_APIC_SIPI
[qemu] kvm_get_vcpu_events
If this is what happens happen, the fix is to call the functions in this
order:
- first kvm_get_vcpu_events
- then kvm_get_mp_state
- then all the others.
This way you have:
VCPU 0 VCPU 1
[qemu] kvm_get_vcpu_events
__apic_accept_irq
set KVM_APIC_SIPI
[qemu] kvm_get_mp_state
[kvm] kvm_apic_accept_events
[kvm] kvm_vcpu_deliver_sipi_vector
// this modifies CS and RIP!!!
[qemu] kvm_getput_regs
// reads RIP
...
[qemu] kvm_getput_sregs
// reads CS
...
and the sipi_vector is never lost.
Paolo
prev parent reply other threads:[~2017-07-12 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 9:12 [Qemu-devel] [PATCH] target-i386:kvm_get/put_vcpu_events don't handle sipi_vector Peng Hao
2017-07-12 17:00 ` Paolo Bonzini [this message]
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=7cdaad86-333a-4b7b-1c91-09ad6e036ecd@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=peng.hao2@zte.com.cn \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).