From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiao Guangrong <guangrong.xiao@linux.intel.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features
Date: Thu, 10 Mar 2016 13:30:51 +0100 [thread overview]
Message-ID: <56E168FB.3080509@redhat.com> (raw)
In-Reply-To: <56E1686F.1060200@linux.intel.com>
On 10/03/2016 13:28, Xiao Guangrong wrote:
>
>> Patch 1 ensures that all aspects of MPX are disabled when eager FPU
>> is disabled on the host. Patch 2 is just a cleanup.
>
> It looks good to me.
>
> Reviewed-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Thanks very much!
> Now, more and more features depend on eger xsave, e.g, fpu, mpx and
> protection-key, maybe it is the time to rename eager-fpu to eager-xsave?
Yeah, that could be possible. You can propose it to Ingo Molnar (CCed).
If you change it in the general purpose kernel code, KVM will of course
follow suit.
Paolo
next prev parent reply other threads:[~2016-03-10 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 11:44 [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features Paolo Bonzini
2016-03-08 11:44 ` [PATCH 1/2] " Paolo Bonzini
[not found] ` <CA+3C=r-NVn__gPVdYRSypzjfejRBgB4VVY5OpckS2QGjXnUu2Q@mail.gmail.com>
2016-03-11 12:09 ` Paolo Bonzini
2016-03-24 13:06 ` Yang Zhang
2016-03-24 13:07 ` Paolo Bonzini
2016-04-13 9:47 ` Yang Zhang
2016-05-10 12:38 ` Paolo Bonzini
2016-03-08 11:44 ` [PATCH 2/2] KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch Paolo Bonzini
2016-03-10 12:28 ` [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features Xiao Guangrong
2016-03-10 12:30 ` Paolo Bonzini [this message]
2016-03-10 17:35 ` Ingo Molnar
2016-03-10 17:38 ` 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=56E168FB.3080509@redhat.com \
--to=pbonzini@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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).