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 3/3] KVM: make make_all_cpus_request() lockless
Date: Wed, 05 Jan 2011 18:08:31 +0800 [thread overview]
Message-ID: <4D24431F.2030205@cn.fujitsu.com> (raw)
In-Reply-To: <4D243FEF.6090105@redhat.com>
On 01/05/2011 05:54 PM, Avi Kivity wrote:
>> + kvm_make_request(req, vcpu);
>> cpu = vcpu->cpu;
>> if (cpus != NULL&& cpu != -1&& cpu != me&&
>> atomic_read(&vcpu->guest_mode))
>> @@ -163,7 +161,7 @@ static bool make_all_cpus_request(struct kvm *kvm, unsigned int req)
>> smp_call_function_many(cpus, ack_flush, NULL, 1);
>> else
>> called = false;
>> - raw_spin_unlock(&kvm->requests_lock);
>> + put_cpu();
>> free_cpumask_var(cpus);
>> return called;
>> }
>
> Maybe we can drop 'cpu != me' and then we don't need to disable preemption?
>
Preemption should be disabled in the caller site of smp_call_function_many():
......
* You must not call this function with disabled interrupts or from a
* hardware interrupt handler or from a bottom half handler. Preemption
* must be disabled when calling this function.
*/
void smp_call_function_many(const struct cpumask *mask,
smp_call_func_t func, void *info, bool wait)
{
......
prev parent reply other threads:[~2011-01-05 10:08 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
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 [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=4D24431F.2030205@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