[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45eb9e95-0ea1-0ff2-b01b-c73ef589ce60@redhat.com>
Date: Thu, 29 Nov 2018 11:13:37 +0100
From: David Hildenbrand <david@...hat.com>
To: Liu Jingqi <jingqi.liu@...el.com>, pbonzini@...hat.com,
rkrcmar@...hat.com, tglx@...utronix.de, mingo@...hat.com
Cc: bp@...en8.de, hpa@...or.com, x86@...nel.org, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, tao3.xu@...el.com
Subject: Re: [PATCH v2 0/2] KVM: x86: expose direct stores instructions into
VM.
On 06.11.18 06:55, Liu Jingqi 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.
>
> 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(-)
>
Does it make sense to squash both patches? (into a patch named just like
this cover letter? :) )
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists