Re: [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features

From	Ingo Molnar <mingo@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features
Date	2016-03-10 18:40 +0100
Message-ID	<rbcJ3-1SN-7@gated-at.bofh.it> (permalink)
References	<raojg-hv-9@gated-at.bofh.it> <rb7T4-6WL-17@gated-at.bofh.it> <rb82J-71L-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

* Paolo Bonzini <pbonzini@redhat.com> wrote:

> > 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.

So we have this queued up for v4.6:

  58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs

and if all goes fine with that then the plan for v4.7 is to remove the lazy FPU 
restore code altogether.

Thanks,

	Ingo

Thread

[PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features Paolo Bonzini <pbonzini@redhat.com> - 2016-03-08 12:50 +0100
  [PATCH 2/2] KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch Paolo Bonzini <pbonzini@redhat.com> - 2016-03-08 12:50 +0100
  Re: [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX  XSAVE features Xiao Guangrong <guangrong.xiao@linux.intel.com> - 2016-03-10 13:30 +0100
    Re: [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX  XSAVE features Paolo Bonzini <pbonzini@redhat.com> - 2016-03-10 13:40 +0100
      Re: [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX  XSAVE features Ingo Molnar <mingo@kernel.org> - 2016-03-10 18:40 +0100
        Re: [PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX  XSAVE features Paolo Bonzini <pbonzini@redhat.com> - 2016-03-10 18:40 +0100

csiph-web