From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Jidong Xiao" <jidong.xiao@gmail.com>
Cc: KVM <kvm@vger.kernel.org>
Subject: Re: How to enable Pause Loop Exiting (PLE)?
Date: Mon, 9 Jun 2014 14:25:02 +0800 [thread overview]
Message-ID: <201406091424598514306@sangfor.com> (raw)
In-Reply-To: CAG4AFWb2_-6gHRvJw2pGQbyp0C+uSbQgU=72aZib7j+DkskEmg@mail.gmail.com
>>>Hi,
>>>
>>>I am using this tool for querying VMX capabilities.
>>>
>>>http://git.qemu.org/?p=qemu.git;a=blob_plain;f=scripts/kvm/vmxcap;hb=HEAD
>>>
>>>And it shows as below that pause-loop exiting is not enabled. My kernel is 3.14.
>>>
>>>secondary processor-based controls
>>> Virtualize APIC accesses yes
>>> Enable EPT yes
>>> Descriptor-table exiting yes
>>> Enable RDTSCP yes
>>> Virtualize x2APIC mode yes
>>> Enable VPID yes
>>> WBINVD exiting yes
>>> Unrestricted guest no
>>> APIC register emulation no
>>> Virtual interrupt delivery no
>>> PAUSE-loop exiting no
>>> RDRAND exiting no
>>> Enable INVPCID no
>>> Enable VM functions no
>>> VMCS shadowing no
>>> EPT-violation #VE no
>>>
>>>What shall I do if I wish to enable PLE? I have also tried this:
>>>
>> From above info, your physical cpu dose not support ple feature,
>> if you want to enable ple, your cpu must support ple feature, and 'PAUSE exiting' must be 0-settting, 'PAUSE-loop exiting' must be 1-setting.
>> And, kvm-intel module will enable ple as default if your cpu support ple feature.
>>
>Hi, Haoyu,
>
>I have another machine, in which Pause Loop Exiting is showing yes,
>but PAUSE Exiting is also showing yes, see below, but you said PAUSE
>exiting must be 0 setting, so what shall I do? Is PLE enabled or not?
>
check /sys/module/kvm_intel/parameters/ple_gap, if non-zero(>0), ple is enabled, zero means ple is disabled.
Thanks,
Zhang Haoyu
>primary processor-based controls
> Interrupt window exiting yes
> Use TSC offsetting yes
> HLT exiting yes
> INVLPG exiting yes
> MWAIT exiting yes
> RDPMC exiting yes
> RDTSC exiting yes
> CR3-load exiting default
> CR3-store exiting default
> CR8-load exiting yes
> CR8-store exiting yes
> Use TPR shadow yes
> NMI-window exiting yes
> MOV-DR exiting yes
> Unconditional I/O exiting yes
> Use I/O bitmaps yes
> Monitor trap flag yes
> Use MSR bitmaps yes
> MONITOR exiting yes
> PAUSE exiting yes
> Activate secondary control yes
>secondary processor-based controls
> Virtualize APIC accesses yes
> Enable EPT yes
> Descriptor-table exiting yes
> Enable RDTSCP yes
> Virtualize x2APIC mode yes
> Enable VPID yes
> WBINVD exiting yes
> Unrestricted guest yes
> APIC register emulation no
> Virtual interrupt delivery no
> PAUSE-loop exiting yes
> RDRAND exiting no
> Enable INVPCID no
> Enable VM functions no
> VMCS shadowing no
> EPT-violation #VE no
next prev parent reply other threads:[~2014-06-09 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 3:52 How to enable Pause Loop Exiting (PLE)? Zhang Haoyu
2014-06-09 4:36 ` Jidong Xiao
2014-06-09 5:56 ` Jidong Xiao
2014-06-09 6:25 ` Zhang Haoyu [this message]
2014-06-09 7:16 ` Zhang Haoyu
2014-06-09 20:27 ` Jidong Xiao
2014-06-09 21:04 ` Liwen Wu (liwwu)
2014-06-10 1:58 ` Zhang Haoyu
-- strict thread matches above, loose matches on Subject: below --
2014-06-08 18:34 Jidong Xiao
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=201406091424598514306@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=jidong.xiao@gmail.com \
--cc=kvm@vger.kernel.org \
/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