From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: don't sent IPI if the vcpu is not online
Date: Sun, 05 Sep 2010 10:18:51 +0300 [thread overview]
Message-ID: <4C83445B.4020103@redhat.com> (raw)
In-Reply-To: <4C807593.1050903@cn.fujitsu.com>
On 09/03/2010 07:12 AM, Xiao Guangrong wrote:
> It's no need sent IPI to the vcpu which is schedule out
>
>
> @@ -86,6 +86,7 @@ struct kvm_vcpu {
> unsigned long requests;
> unsigned long guest_debug;
> int srcu_idx;
> + bool online;
Why not check for guest_mode instead?
>
> int fpu_active;
> int guest_fpu_loaded, guest_xcr0_loaded;
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 9a73b98..998cbc8 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -148,8 +148,9 @@ static bool make_all_cpus_request(struct kvm *kvm, unsigned int req)
> raw_spin_lock(&kvm->requests_lock);
> me = smp_processor_id();
> kvm_for_each_vcpu(i, vcpu, kvm) {
> - if (kvm_make_check_request(req, vcpu))
> + if (kvm_make_check_request(req, vcpu) || !vcpu->online)
> continue;
> +
> cpu = vcpu->cpu;
> if (cpus != NULL&& cpu != -1&& cpu != me)
> cpumask_set_cpu(cpu, cpus);
btw, I think a more important optimization would be to drop
kvm->requests_lock. But I have no idea how to do it.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-09-05 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 4:12 [PATCH] KVM: don't sent IPI if the vcpu is not online Xiao Guangrong
2010-09-05 7:18 ` Avi Kivity [this message]
2010-09-06 1:48 ` Xiao Guangrong
2010-09-06 5:46 ` Avi Kivity
2010-09-06 8:51 ` Alexander Graf
2010-09-06 8:55 ` Avi Kivity
2010-09-06 8:59 ` Alexander Graf
2010-09-06 9:05 ` Avi Kivity
2010-09-06 9:09 ` Alexander Graf
2010-09-06 9:14 ` Avi Kivity
2010-09-06 9:19 ` Alexander Graf
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=4C83445B.4020103@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@cn.fujitsu.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