From: Tao Xu <tao3.xu@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"mtosatti@redhat.com" <mtosatti@redhat.com>
Cc: "Liu, Jingqi" <jingqi.liu@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] x86: Enable user wait instructions
Date: Wed, 9 Oct 2019 09:03:15 +0800 [thread overview]
Message-ID: <032bc3fa-d950-a30a-cb95-8fb11b398fd2@intel.com> (raw)
In-Reply-To: <20190929015718.19562-1-tao3.xu@intel.com>
Ping for comments :)
On 9/29/2019 9:57 AM, Xu, Tao3 wrote:
> UMONITOR, UMWAIT and TPAUSE are a set of user wait instructions.
>
> UMONITOR arms address monitoring hardware using an address. A store
> to an address within the specified address range triggers the
> monitoring hardware to wake up the processor waiting in umwait.
>
> UMWAIT instructs the processor to enter an implementation-dependent
> optimized state while monitoring a range of addresses. The optimized
> state may be either a light-weight power/performance optimized state
> (c0.1 state) or an improved power/performance optimized state
> (c0.2 state).
>
> TPAUSE instructs the processor to enter an implementation-dependent
> optimized state c0.1 or c0.2 state and wake up when time-stamp counter
> reaches specified timeout.
>
> Availability of the user wait instructions is indicated by the presence
> of the CPUID feature flag WAITPKG CPUID.0x07.0x0:ECX[5].
>
> The patches enable the umonitor, umwait and tpause features in KVM.
> Because umwait and tpause can put a (psysical) CPU into a power saving
> state, by default we dont't expose it in kvm and provide a capability to
> enable it. Use kvm capability to enable UMONITOR, UMWAIT and TPAUSE when
> QEMU use "-overcommit cpu-pm=on, a VM can use UMONITOR, UMWAIT and TPAUSE
> instructions. If the instruction causes a delay, the amount of time
> delayed is called here the physical delay. The physical delay is first
> computed by determining the virtual delay (the time to delay relative to
> the VM’s timestamp counter). Otherwise, UMONITOR, UMWAIT and TPAUSE cause
> an invalid-opcode exception(#UD).
>
> The release document ref below link:
> https://software.intel.com/sites/default/files/\
> managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf
>
> Changelog:
> v5:
> Remove CPUID_7_0_ECX_WAITPKG if enable_cpu_pm is not set. (Paolo)
> v4:
> Set IA32_UMWAIT_CONTROL 32bits
> v3:
> Simplify the patches, expose user wait instructions when the guest
> has CPUID (Paolo)
> v2:
> Separated from the series
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg549526.html
> Use kvm capability to enable UMONITOR, UMWAIT and TPAUSE when
> QEMU use "-overcommit cpu-pm=on"
> v1:
> Sent out with MOVDIRI/MOVDIR64B instructions patches
>
> Tao Xu (2):
> x86/cpu: Add support for UMONITOR/UMWAIT/TPAUSE
> target/i386: Add support for save/load IA32_UMWAIT_CONTROL MSR
>
> target/i386/cpu.c | 3 ++-
> target/i386/cpu.h | 3 +++
> target/i386/kvm.c | 19 +++++++++++++++++++
> target/i386/machine.c | 20 ++++++++++++++++++++
> 4 files changed, 44 insertions(+), 1 deletion(-)
>
prev parent reply other threads:[~2019-10-09 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 1:57 [PATCH v5 0/2] x86: Enable user wait instructions Tao Xu
2019-09-29 1:57 ` [PATCH v5 1/2] x86/cpu: Add support for UMONITOR/UMWAIT/TPAUSE Tao Xu
2019-10-09 8:06 ` Paolo Bonzini
2019-10-09 8:21 ` Tao Xu
2019-09-29 1:57 ` [PATCH v5 2/2] target/i386: Add support for save/load IA32_UMWAIT_CONTROL MSR Tao Xu
2019-10-09 1:03 ` Tao Xu [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=032bc3fa-d950-a30a-cb95-8fb11b398fd2@intel.com \
--to=tao3.xu@intel.com \
--cc=ehabkost@redhat.com \
--cc=jingqi.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).