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

On 10/03/2016 18:35, Ingo Molnar wrote: > 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. Whoa. Unexpected, but I cannot say I'm

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

On 10/03/2016 18:35, Ingo Molnar wrote: > 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. Whoa. Unexpected, but I cannot say I'm

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

* Paolo Bonzini 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

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

* Paolo Bonzini 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

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

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 Thanks very much! > Now, more

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

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 Thanks very much! > Now, more and more features depend on

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

On 03/08/2016 07:44 PM, Paolo Bonzini 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 Now, more and more features depend on eger

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

On 03/08/2016 07:44 PM, Paolo Bonzini 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 Now, more and more features depend on eger xsave, e.g, fpu, mpx and

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

Patch 1 ensures that all aspects of MPX are disabled when eager FPU is disabled on the host. Patch 2 is just a cleanup. Paolo Bonzini (2): KVM: x86: disable MPX if host did not enable MPX XSAVE features KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch

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

Patch 1 ensures that all aspects of MPX are disabled when eager FPU is disabled on the host. Patch 2 is just a cleanup. Paolo Bonzini (2): KVM: x86: disable MPX if host did not enable MPX XSAVE features KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch