Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1364142 > unrolled thread
| Started by | Paolo Bonzini <pbonzini@redhat.com> |
|---|---|
| First post | 2016-03-24 14:10 +0100 |
| Last post | 2016-03-24 14:10 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH 1/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features Paolo Bonzini <pbonzini@redhat.com> - 2016-03-24 14:10 +0100
| From | Paolo Bonzini <pbonzini@redhat.com> |
|---|---|
| Date | 2016-03-24 14:10 +0100 |
| Subject | Re: [PATCH 1/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features |
| Message-ID | <rgdbr-34K-1@gated-at.bofh.it> |
On 24/03/2016 14:06, Yang Zhang wrote: > > I mean why not keep the old way that only activate the eager_fpu while > guest sees the MPX bit in CPUID, like: > > vcpu->arch.eager_fpu = use_eager_fpu() && guest_cpuid_has_mpx(vcpu); If the host uses eager FPU you can assume that it's faster than lazy FPU. Paolo > Besides, vmx_fpu_activate is called when do vcpu_reset. So it seems no > need to call fpu_activate() here again.
Back to top | Article view | linux.kernel
csiph-web