From: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/3] KVM: send IPI to vcpu only when it's in guest mode
Date: Wed, 05 Jan 2011 18:05:35 +0800 [thread overview]
Message-ID: <4D24426F.5090000@cn.fujitsu.com> (raw)
In-Reply-To: <4D243E69.60603@redhat.com>
On 01/05/2011 05:48 PM, Avi Kivity wrote:
>> srcu_read_unlock(&vcpu->kvm->srcu, idx);
>> + atomic_set(&vcpu->guest_mode, 1);
>> kvm_guest_enter();
>
> I think it needs an smp_wmb() (technically x86 needs it too, but x86 is strongly ordered)
......
>> - if (cpus != NULL&& cpu != -1&& cpu != me)
>> + if (cpus != NULL&& cpu != -1&& cpu != me&&
>> + atomic_read(&vcpu->guest_mode))
>> cpumask_set_cpu(cpu, cpus);
>
> and smp_rmb() before the atomic_read().
Yeah, you're right, i'll fix these in the next version.
>
>> }
>> if (unlikely(cpus == NULL))
>
> Not sure if this is an optimization. On one hand it removes an expensive IPI for the fraction of time the cpu is out of guest mode. On the other hand it adds an unconditional cacheline bounce (and bounce back).
>
> Hm. I see that ->guest_mode and ->requests are in fact in the same cache line. So this is likely really an optimization. We should probably reorganize kvm_vcpu so that this is made explicit.
>
OK, will do it in the separate patch in the future, thanks!
next prev parent reply other threads:[~2011-01-05 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 9:36 [PATCH 1/3] KVM: fix rcu usage warning in kvm_arch_vcpu_ioctl_set_sregs() Xiao Guangrong
2011-01-05 9:38 ` [PATCH 2/3] KVM: send IPI to vcpu only when it's in guest mode Xiao Guangrong
2011-01-05 9:48 ` Avi Kivity
2011-01-05 10:05 ` Xiao Guangrong [this message]
2011-01-06 3:58 ` Xiao Guangrong
2011-01-05 9:40 ` [PATCH 3/3] KVM: make make_all_cpus_request() lockless Xiao Guangrong
2011-01-05 9:54 ` Avi Kivity
2011-01-05 10:08 ` Xiao Guangrong
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=4D24426F.5090000@cn.fujitsu.com \
--to=xiaoguangrong@cn.fujitsu.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox