mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liu Jingqi <jingqi.liu@intel.com>
To: pbonzini@redhat.com, rkrcmar@redhat.com, tglx@linutronix.de,
	mingo@redhat.com
Cc: bp@alien8.de, hpa@zytor.com, x86@kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, tao3.xu@intel.com,
	Liu Jingqi <jingqi.liu@intel.com>
Subject: [PATCH v2 0/2] KVM: x86: expose direct stores instructions into VM.
Date: Tue,  6 Nov 2018 13:55:26 +0800	[thread overview]
Message-ID: <1541483728-7826-1-git-send-email-jingqi.liu@intel.com> (raw)

Direct stores instructions MOVDIRI and MOVDIR64B will be available in
Tremont and other future x86 processors,
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 movdiri and movdir64b features to guest VM.

Changelog:
v2:
	Separated from the series https://lkml.org/lkml/2018/7/10/160
	since umonitor/umwait/tpause instructions patches are not ready yet.
v1:
	Sent out with umonitor/umwait/tpause instructions patches.

Liu Jingqi (2):
  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(-)

-- 
2.7.4


             reply	other threads:[~2018-11-06  6:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06  5:55 Liu Jingqi [this message]
2018-11-06  5:55 ` [PATCH v2 1/2] KVM: x86: expose MOVDIRI CPU feature " Liu Jingqi
2018-11-06  5:55 ` [PATCH v2 2/2] KVM: x86: expose MOVDIR64B " Liu Jingqi
2018-11-29 10:13 ` [PATCH v2 0/2] KVM: x86: expose direct stores instructions " David Hildenbrand
2018-11-30 20:41 ` Eric Northup
2019-01-30 17:15   ` Paolo Bonzini
2019-01-30 17:16 ` 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=1541483728-7826-1-git-send-email-jingqi.liu@intel.com \
    --to=jingqi.liu@intel.com \
    --cc=bp@alien8.de \
    --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=tao3.xu@intel.com \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®