From: Avi Kivity <avi@redhat.com>
To: "Nadav Har'El" <nyh@il.ibm.com>
Cc: kvm@vger.kernel.org, gleb@redhat.com
Subject: Re: [PATCH 25/28] nVMX: Further fixes for lazy FPU loading
Date: Thu, 09 Dec 2010 15:05:30 +0200 [thread overview]
Message-ID: <4D00D41A.2000900@redhat.com> (raw)
In-Reply-To: <201012081712.oB8HCkpY008822@rice.haifa.ibm.com>
On 12/08/2010 07:12 PM, Nadav Har'El wrote:
> KVM's "Lazy FPU loading" means that sometimes L0 needs to set CR0.TS, even
> if a guest didn't set it. Moreover, L0 must also trap CR0.TS changes and
> NM exceptions, even if we have a guest hypervisor (L1) who didn't want these
> traps. And of course, conversely: If L1 wanted to trap these events, we
> must let it, even if L0 is not interested in them.
>
> This patch fixes some existing KVM code (in update_exception_bitmap(),
> vmx_fpu_activate(), vmx_fpu_deactivate()) to do the correct merging of L0's
> and L1's needs. Note that handle_cr() was already fixed in the above patch,
> and that new code in introduced in previous patches already handles CR0
> correctly (see prepare_vmcs02(), prepare_vmcs12(), and nested_vmx_vmexit()).
>
>
> @@ -1415,8 +1424,19 @@ static void vmx_fpu_activate(struct kvm_
> cr0&= ~(X86_CR0_TS | X86_CR0_MP);
> cr0 |= kvm_read_cr0_bits(vcpu, X86_CR0_TS | X86_CR0_MP);
> vmcs_writel(GUEST_CR0, cr0);
> - update_exception_bitmap(vcpu);
> vcpu->arch.cr0_guest_owned_bits = X86_CR0_TS;
> + if (is_guest_mode(vcpu)) {
> + /* While we (L0) no longer care about NM exceptions or cr0.TS
> + * changes, our guest hypervisor (L1) might care in which case
> + * we must trap them for it.
> + */
> + u32 eb = vmcs_read32(EXCEPTION_BITMAP)& ~(1u<< NM_VECTOR);
> + struct vmcs_fields *vmcs12 = get_vmcs12_fields(vcpu);
> + eb |= vmcs12->exception_bitmap;
> + vcpu->arch.cr0_guest_owned_bits&= ~vmcs12->cr0_guest_host_mask;
> + vmcs_write32(EXCEPTION_BITMAP, eb);
> + } else
> + update_exception_bitmap(vcpu);
Isn't update_exception_bitmap() sufficient for both cases?
> vmcs_writel(CR0_GUEST_HOST_MASK, ~vcpu->arch.cr0_guest_owned_bits);
> }
>
> @@ -1424,12 +1444,24 @@ static void vmx_decache_cr0_guest_bits(s
>
> static void vmx_fpu_deactivate(struct kvm_vcpu *vcpu)
> {
> + /* Note that there is no vcpu->fpu_active = 0 here. The caller must
> + * set this *before* calling this function.
> + */
> vmx_decache_cr0_guest_bits(vcpu);
> vmcs_set_bits(GUEST_CR0, X86_CR0_TS | X86_CR0_MP);
> - update_exception_bitmap(vcpu);
> + vmcs_write32(EXCEPTION_BITMAP,
> + vmcs_read32(EXCEPTION_BITMAP) | (1u<< NM_VECTOR));
Why not fold the logic into update_exception_bitmap()?
> vcpu->arch.cr0_guest_owned_bits = 0;
> vmcs_writel(CR0_GUEST_HOST_MASK, ~vcpu->arch.cr0_guest_owned_bits);
> - vmcs_writel(CR0_READ_SHADOW, vcpu->arch.cr0);
> + if (is_guest_mode(vcpu))
> + /* Unfortunately in nested mode we play with arch.cr0's PG
> + * bit, so we musn't copy it all, just the relevant TS bit
> + */
> + vmcs_writel(CR0_READ_SHADOW,
> + (vmcs_readl(CR0_READ_SHADOW)& ~X86_CR0_TS) |
> + (vcpu->arch.cr0& X86_CR0_TS));
> + else
> + vmcs_writel(CR0_READ_SHADOW, vcpu->arch.cr0);
Didn't you have a nice guest_readable_cr0() function that did this?
> }
>
> static unsigned long vmx_get_rflags(struct kvm_vcpu *vcpu)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-09 13:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 16:59 [PATCH 0/28] nVMX: Nested VMX, v7 Nadav Har'El
2010-12-08 17:00 ` [PATCH 01/28] nVMX: Add "nested" module option to vmx.c Nadav Har'El
2010-12-08 17:00 ` [PATCH 02/28] nVMX: Add VMX and SVM to list of supported cpuid features Nadav Har'El
2010-12-09 11:38 ` Joerg Roedel
2010-12-15 13:25 ` Nadav Har'El
2010-12-08 17:01 ` [PATCH 03/28] nVMX: Implement VMXON and VMXOFF Nadav Har'El
2010-12-08 17:02 ` [PATCH 04/28] nVMX: Allow setting the VMXE bit in CR4 Nadav Har'El
2010-12-08 17:02 ` [PATCH 05/28] nVMX: Introduce vmcs12: a VMCS structure for L1 Nadav Har'El
2010-12-08 17:03 ` [PATCH 06/28] nVMX: Implement reading and writing of VMX MSRs Nadav Har'El
2010-12-09 11:04 ` Avi Kivity
2010-12-08 17:03 ` [PATCH 07/28] nVMX: Decoding memory operands of VMX instructions Nadav Har'El
2010-12-09 11:08 ` Avi Kivity
2010-12-08 17:04 ` [PATCH 08/28] nVMX: Hold a vmcs02 for each vmcs12 Nadav Har'El
2010-12-09 12:41 ` Avi Kivity
2010-12-08 17:04 ` [PATCH 09/28] nVMX: Add VMCS fields to the vmcs12 Nadav Har'El
2010-12-09 12:43 ` Avi Kivity
2010-12-10 12:10 ` Nadav Har'El
2010-12-08 17:05 ` [PATCH 10/28] nVMX: Success/failure of VMX instructions Nadav Har'El
2010-12-08 17:05 ` [PATCH 11/28] nVMX: Implement VMCLEAR Nadav Har'El
2010-12-08 17:06 ` [PATCH 12/28] nVMX: Implement VMPTRLD Nadav Har'El
2010-12-08 17:06 ` [PATCH 13/28] nVMX: Implement VMPTRST Nadav Har'El
2010-12-08 17:07 ` [PATCH 14/28] nVMX: Implement VMREAD and VMWRITE Nadav Har'El
2010-12-08 17:07 ` [PATCH 15/28] nVMX: Prepare vmcs02 from vmcs01 and vmcs12 Nadav Har'El
2010-12-08 17:08 ` [PATCH 16/28] nVMX: Move register-syncing to a function Nadav Har'El
2010-12-08 17:08 ` [PATCH 17/28] nVMX: Implement VMLAUNCH and VMRESUME Nadav Har'El
2010-12-08 17:09 ` [PATCH 18/28] nVMX: No need for handle_vmx_insn function any more Nadav Har'El
2010-12-08 17:09 ` [PATCH 19/28] nVMX: Exiting from L2 to L1 Nadav Har'El
2010-12-09 12:55 ` Avi Kivity
2010-12-08 17:10 ` [PATCH 20/28] nVMX: Deciding if L0 or L1 should handle an L2 exit Nadav Har'El
2010-12-08 17:10 ` [PATCH 21/28] nVMX: Correct handling of interrupt injection Nadav Har'El
2010-12-08 17:11 ` [PATCH 22/28] nVMX: Correct handling of exception injection Nadav Har'El
2010-12-08 17:11 ` [PATCH 23/28] nVMX: Correct handling of idt vectoring info Nadav Har'El
2010-12-08 17:12 ` [PATCH 24/28] nVMX: Handling of CR0 and CR4 modifying instructions Nadav Har'El
2010-12-09 13:19 ` Avi Kivity
2010-12-08 17:12 ` [PATCH 25/28] nVMX: Further fixes for lazy FPU loading Nadav Har'El
2010-12-09 13:05 ` Avi Kivity [this message]
2010-12-08 17:13 ` [PATCH 26/28] nVMX: Additional TSC-offset handling Nadav Har'El
2010-12-08 17:13 ` [PATCH 27/28] nVMX: Miscellenous small corrections Nadav Har'El
2010-12-08 17:14 ` [PATCH 28/28] nVMX: Documentation Nadav Har'El
2010-12-09 12:44 ` [PATCH 0/28] nVMX: Nested VMX, v7 Avi Kivity
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=4D00D41A.2000900@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nyh@il.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.