From: Jingqi Liu <jingqi.liu@intel.com>
To: pbonzini@redhat.com, rkrcmar@redhat.com, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com
Cc: x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, wei.w.wang@intel.com,
Jingqi Liu <jingqi.liu@intel.com>
Subject: [PATCH 0/3] KVM: x86: expose a few new features into VM.
Date: Tue, 10 Jul 2018 16:54:40 +0800 [thread overview]
Message-ID: <1531212883-63173-1-git-send-email-jingqi.liu@intel.com> (raw)
A few new features including user wait (umwait, umonitor, tpause)
and direct stores (movdiri and movdir64b) will be available in
Intel Snow Ridge, and need to be exposed to guest VM.
The release document ref below link:
https://software.intel.com/sites/default/files/managed/c5/15/\
architecture-instruction-set-extensions-programming-reference.pdf
This series expose umonitor,umwait, tpause, movdiri and movdir64b
features to guest VM.
Jingqi Liu (3):
KVM: x86: expose UMWAIT/UMONITOR/TPAUSE CPU features into VM.
KVM: x86: expose MOVDIRI CPU feature into VM.
KVM: x86: expose MOVDIR64B CPU feature into VM.
arch/x86/kvm/cpuid.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2018-07-10 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 8:54 Jingqi Liu [this message]
2018-07-10 8:54 ` [PATCH 1/3] KVM: x86: expose UMWAIT/UMONITOR/TPAUSE CPU features into VM Jingqi Liu
2018-07-10 11:53 ` kbuild test robot
2018-07-10 12:12 ` kbuild test robot
2018-08-20 10:16 ` Paolo Bonzini
2018-08-20 12:36 ` Liu, Jingqi
2018-07-10 8:54 ` [PATCH 2/3] KVM: x86: expose MOVDIRI CPU feature " Jingqi Liu
2018-07-10 12:25 ` kbuild test robot
2018-07-10 8:54 ` [PATCH 3/3] KVM: x86: expose MOVDIR64B " Jingqi Liu
2018-07-10 10:04 ` kbuild test robot
2018-08-06 8:17 ` [PATCH 0/3] KVM: x86: expose a few new features " Liu, Jingqi
2018-08-06 16:58 ` Paolo Bonzini
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=1531212883-63173-1-git-send-email-jingqi.liu@intel.com \
--to=jingqi.liu@intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=wei.w.wang@intel.com \
--cc=x86@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