From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthoine Bourgeois <bourgeois@bertin.fr>
Cc: Gleb Natapov <gleb@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] kvm, vmx: Fix lazy FPU on nested guest
Date: Wed, 13 Nov 2013 18:46:47 +0100 [thread overview]
Message-ID: <5283BB07.8000504@redhat.com> (raw)
In-Reply-To: <20131113104533.GA14780@bertin.fr>
Il 13/11/2013 11:45, Anthoine Bourgeois ha scritto:
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 2b2fce1..e33cadf 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -6627,6 +6627,9 @@ static bool nested_vmx_exit_handled(struct
> kvm_vcpu *vcpu)
> return 0;
> else if (is_page_fault(intr_info))
> return enable_ept;
> + else if (is_no_device(intr_info) &&
> + !(nested_read_cr0(vmcs12) & X86_CR0_TS))
> + return 0;
> return vmcs12->exception_bitmap &
> (1u << (intr_info & INTR_INFO_VECTOR_MASK));
> case EXIT_REASON_EXTERNAL_INTERRUPT:
> --
The whitespace in this patch is corrupted. For this time I applied it;
next time however please use "git send-email".
Paolo
next prev parent reply other threads:[~2013-11-13 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 10:45 [PATCH] kvm, vmx: Fix lazy FPU on nested guest Anthoine Bourgeois
2013-11-13 17:46 ` Paolo Bonzini [this message]
2013-11-14 7:22 ` Anthoine Bourgeois
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=5283BB07.8000504@redhat.com \
--to=pbonzini@redhat.com \
--cc=bourgeois@bertin.fr \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
/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