From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/6 v2] Lazy fpu for svm/npt
Date: Mon, 11 Jan 2010 12:39:06 +0200 [thread overview]
Message-ID: <4B4AFFCA.9080601@redhat.com> (raw)
In-Reply-To: <20100111103226.GA4498@amd.com>
On 01/11/2010 12:32 PM, Joerg Roedel wrote:
> On Sun, Jan 10, 2010 at 12:31:23PM +0200, Avi Kivity wrote:
>
>> This patchset (on top of the previous cr0 patchset) brings lazy fpu to npt.
>> For the cases where guest and host cr0 match (the majority) it will disable
>> intercepts for cr0.ts once the guest fpu is loaded, so the guest can to its
>> own lazy fpu without trapping.
>>
> Looks good to me.
>
> Acked-by: Joerg Roedel<joerg.roedel@amd.com>
>
Now merged, along with the earlier vmx-related bits.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-01-11 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 10:31 [PATCH 0/6 v2] Lazy fpu for svm/npt Avi Kivity
2010-01-10 10:31 ` [PATCH 1/6] KVM: Set cr0.et when the guest writes cr0 Avi Kivity
2010-01-10 10:31 ` [PATCH 2/6] KVM: SVM: Fix SVM_CR0_SELECTIVE_MASK Avi Kivity
2010-01-10 10:31 ` [PATCH 3/6] KVM: SVM: Initialize fpu_active in init_vmcb() Avi Kivity
2010-01-10 10:31 ` [PATCH 4/6] KVM: SVM: Restore unconditional cr0 intercept under npt Avi Kivity
2010-01-10 10:31 ` [PATCH 5/6] KVM: SVM: Selective cr0 intercept Avi Kivity
2010-01-10 10:31 ` [PATCH 6/6] KVM: SVM: Lazy fpu with npt Avi Kivity
2010-01-11 10:32 ` [PATCH 0/6 v2] Lazy fpu for svm/npt Joerg Roedel
2010-01-11 10:39 ` Avi Kivity [this message]
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=4B4AFFCA.9080601@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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.