From: Eric Northup <digitaleric@google.com>
To: jingqi.liu@intel.com
Cc: Paolo Bonzini <pbonzini@redhat.com>,
rkrcmar@redhat.com, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
bp@alien8.de, "H. Peter Anvin" <hpa@zytor.com>,
"the arch/x86 maintainers" <x86@kernel.org>,
KVM <kvm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tao3.xu@intel.com
Subject: Re: [PATCH v2 0/2] KVM: x86: expose direct stores instructions into VM.
Date: Fri, 30 Nov 2018 12:41:44 -0800 [thread overview]
Message-ID: <CAG7+5M0XNw6KOTw6JyqT67fp3cAX=MseT1A0_1Zpb6UM_O3fLw@mail.gmail.com> (raw)
In-Reply-To: <1541483728-7826-1-git-send-email-jingqi.liu@intel.com>
On Mon, Nov 5, 2018 at 10:01 PM Liu Jingqi <jingqi.liu@intel.com> wrote:
>
> Direct stores instructions MOVDIRI and MOVDIR64B will be available in
> Tremont and other future x86 processors,
> and need to be exposed to guest VM.
It seems like KVM's emulator should be able to complete these
instructions to emulated MMIO before exposing CPUID to guests in any
default or supported configurations.
It'll be much simpler for usermode to implement that property if the
KVM-reported supported CPUID table doesn't get updated before the KVM
emulator does.
-Eric
next prev parent reply other threads:[~2018-11-30 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 5:55 [PATCH v2 0/2] KVM: x86: expose direct stores instructions into VM Liu Jingqi
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 [this message]
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='CAG7+5M0XNw6KOTw6JyqT67fp3cAX=MseT1A0_1Zpb6UM_O3fLw@mail.gmail.com' \
--to=digitaleric@google.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jingqi.liu@intel.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;
as well as URLs for NNTP newsgroup(s).