From: Xiao Guangrong <xiaoguangrong.eric@gmail.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: fix missed memory synchronization when patch hypercall
Date: Sun, 09 Jun 2013 18:01:45 +0800 [thread overview]
Message-ID: <51B45289.6080704@gmail.com> (raw)
In-Reply-To: <20130609093910.GL4725@redhat.com>
On 06/09/2013 05:39 PM, Gleb Natapov wrote:
> On Sun, Jun 09, 2013 at 05:29:37PM +0800, Xiao Guangrong wrote:
>> On 06/09/2013 04:45 PM, Gleb Natapov wrote:
>>
>>> +static int emulator_fix_hypercall(struct x86_emulate_ctxt *ctxt)
>>> +{
>>> + struct kvm_vcpu *vcpu = emul_to_vcpu(ctxt);
>>> + return kvm_exec_with_stopped_vcpu(vcpu->kvm,
>>> + emulator_fix_hypercall_cb, ctxt);
>>> +}
>>> +
>>> +
>>> /*
>>> * Check if userspace requested an interrupt window, and that the
>>> * interrupt window is open.
>>> @@ -5761,6 +5769,10 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu)
>>> kvm_deliver_pmi(vcpu);
>>> if (kvm_check_request(KVM_REQ_SCAN_IOAPIC, vcpu))
>>> vcpu_scan_ioapic(vcpu);
>>> + if (kvm_check_request(KVM_REQ_STOP_VCPU, vcpu)){
>>> + mutex_lock(&vcpu->kvm->lock);
>>> + mutex_unlock(&vcpu->kvm->lock);
>>
>> We should execute a serializing instruction here?
>>
>>> --- a/virt/kvm/kvm_main.c
>>> +++ b/virt/kvm/kvm_main.c
>>> @@ -222,6 +222,18 @@ void kvm_make_scan_ioapic_request(struct kvm *kvm)
>>> make_all_cpus_request(kvm, KVM_REQ_SCAN_IOAPIC);
>>> }
>>>
>>> +int kvm_exec_with_stopped_vcpu(struct kvm *kvm, int (*cb)(void *), void *data)
>>> +{
>>> + int r;
>>> +
>>> + mutex_lock(&kvm->lock);
>>> + make_all_cpus_request(kvm, KVM_REQ_STOP_VCPU);
>>> + r = cb(data);
>>
>> And here?
> Since the serialisation instruction the SDM suggest to use is CPUID I
> think the point here is to flush CPU pipeline. Since all vcpus are out
> of a guest mode I think out of order execution of modified instruction
> is no an issue here.
I checked the SDM that it did not said VMLAUNCH/VMRESUME are the
serializing instructions both in VM-Entry description and Instruction
reference, instead it said the VMX related serializing instructions are:
INVEPT, INVVPID.
So, i guess the explicit serializing instruction is needed here.
next prev parent reply other threads:[~2013-06-09 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-08 3:15 [PATCH] KVM: x86: fix missed memory synchronization when patch hypercall Xiao Guangrong
2013-06-09 8:45 ` Gleb Natapov
2013-06-09 8:56 ` Xiao Guangrong
2013-06-09 8:59 ` Gleb Natapov
2013-06-09 9:08 ` Xiao Guangrong
2013-06-09 9:29 ` Xiao Guangrong
2013-06-09 9:39 ` Gleb Natapov
2013-06-09 10:01 ` Xiao Guangrong [this message]
2013-06-09 10:19 ` Gleb Natapov
2013-06-09 11:25 ` Xiao Guangrong
2013-06-09 11:36 ` Gleb Natapov
2013-06-09 11:44 ` Xiao Guangrong
2013-06-09 11:56 ` Gleb Natapov
2013-06-09 12:17 ` Xiao Guangrong
2013-06-09 12:27 ` Gleb Natapov
2013-06-09 12:52 ` Xiao Guangrong
2013-06-18 14:13 ` Paolo Bonzini
2013-06-18 15:22 ` Gleb Natapov
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=51B45289.6080704@gmail.com \
--to=xiaoguangrong.eric@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.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 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.