From: Paolo Bonzini <pbonzini@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "gleb@redhat.com" <gleb@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"Ren, Qiaowei" <qiaowei.ren@intel.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/4] X86/KVM: enable Intel MPX for KVM
Date: Tue, 18 Feb 2014 10:18:57 +0100 [thread overview]
Message-ID: <53032581.7050406@redhat.com> (raw)
In-Reply-To: <52DFB382.5080002@redhat.com>
Il 22/01/2014 13:03, Paolo Bonzini ha scritto:
> Il 22/01/2014 06:29, Liu, Jinsong ha scritto:
>> These patches are version 3 to enalbe Intel MPX for KVM.
>>
>> Version 1:
>> * Add some Intel MPX definiation
>> * Fix a cpuid(0x0d, 0) exposing bug, dynamic per XCR0 features
>> enable/disable
>> * vmx and msr handle for MPX support at KVM
>> * enalbe MPX feature for guest
>>
>> Version 2:
>> * remove generic MPX definiation, Qiaowei's patch has add the
>> definiation at kernel side
>> * add MSR_IA32_BNDCFGS to msrs_to_save
>>
>> Version 3:
>> * rebase on latest kernel, which include Qiaowei's MPX common
>> definiation pulled from HPA's tree
>
> I am afraid there is still some work to do on these patches, so they
> need to be delayed to 3.15.
>
> Patch 1:
> this seems mostly separate from the rest of the MPX work. I
> commented on the missing "ULL" suffix, but I would also like to
> understand why you put this patch in this series.
>
> Patch 2:
> As remarked in the reply to this patch:
> - the vmx_disable_intercept_for_msr has to be unconditional
> - you need a new kvm_x86_ops member mpx_supported, to disable
> MPX whenever the two VMX controls are not available.
>
> Patch 3:
> this patch needs to be rebased. Apart from that it is fine,
> but please move the VMX bits together with patch 2, and the
> other bits together with patch 4.
>
> Patch 4:
> this patch needs to be rebased and to use the new mpx_supported
> member
>
> If you also want to look at nested VMX support for MPX, that would be
> nice. It should not be hard. Otherwise we can take care of that later.
>
> Thanks for your work,
>
> Paolo
Are you going to send v4?
Paolo
next prev parent reply other threads:[~2014-02-18 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 5:29 [Qemu-devel] [PATCH v3 0/4] X86/KVM: enable Intel MPX for KVM Liu, Jinsong
2014-01-22 12:03 ` Paolo Bonzini
2014-02-18 9:18 ` Paolo Bonzini [this message]
2014-02-18 9:32 ` Liu, Jinsong
2014-02-21 18:01 ` Liu, Jinsong
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=53032581.7050406@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jinsong.liu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=qiaowei.ren@intel.com \
/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).