From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: "Wubin (H)" <wu.wubin@huawei.com>,
zhaoshenglong <zhaoshenglong@huawei.com>,
kvm <kvm@vger.kernel.org>
Subject: A problem about optimize the kvm_vcpu_on_spin
Date: Mon, 14 Nov 2016 09:44:57 +0800 [thread overview]
Message-ID: <58291719.4020401@huawei.com> (raw)
Hi Paolo and Radim,
Intel sdm vol3 ch-25.1.3 (p-1074) said: The “PAUSE-loop exiting” VM-execution
control is ignored if CPL > 0.
Does this means that only guest's kernelspace spinlock could causes VMexit due
to "pause-loop exiting" ?
If so, I think the kvm_vcpu_on_spin should selects a (currently not running)vcpu
which cpl=0 to boost, because the cpl>0 vcpus are not the lock-holder. (suppose
the guest isn't RT-linux)
What about your opinion ?
--
Regards,
Longpeng(Mike)
next reply other threads:[~2016-11-14 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 1:44 Longpeng (Mike) [this message]
2016-11-14 8:56 ` A problem about optimize the kvm_vcpu_on_spin Paolo Bonzini
2016-11-14 9:30 ` Longpeng (Mike)
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=58291719.4020401@huawei.com \
--to=longpeng2@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=wu.wubin@huawei.com \
--cc=zhaoshenglong@huawei.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;
as well as URLs for NNTP newsgroup(s).