From: Wei Huang <wei.huang2@amd.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
KeirFraser <keir@xen.org>
Subject: Re: [PATCH] FPU LWP 6/8: create lazy and non-lazy FPU restore functions
Date: Wed, 4 May 2011 11:33:55 -0500 [thread overview]
Message-ID: <4DC17FF3.5080706@amd.com> (raw)
In-Reply-To: <4DC117D6020000780003F9CB@vpn.id2.novell.com>
Checking whether there is a non-lazy state to save is architectural
specific and very messy. For instance, we need to read LWP_CBADDR to
confirm LWP's dirty state. This MSR is AMD specific and we don't want to
add it here. Plus reading data from LWP_CBADDR MSR might be as expensive
as clts/stts.
My previous email showed that the overhead with LWP is around 1%-2% of
__context_switch(). For non lwp-capable CPU, this overhead should be
much smaller (only clts and stts) because xfeature_mask[LWP] is 0.
Yes, clts() and stts() don't have to called every time. How about this one?
/* Restore FPU state whenever VCPU is schduled in. */
void vcpu_restore_fpu_eager(struct vcpu *v)
{
ASSERT(!is_idle_vcpu(v));
/* save the nonlazy extended state which is not tracked by CR0.TS bit */
if ( xsave_enabled(v) )
{
/* Avoid recursion */
clts();
fpu_xrstor(v, XSTATE_NONLAZY);
stts();
}
.
On 05/04/2011 02:09 AM, Jan Beulich wrote:
>>>> On 03.05.11 at 22:17, Wei Huang<wei.huang2@amd.com> wrote:
> Again as pointed out earlier, ...
>
>> --- a/xen/arch/x86/domain.c Tue May 03 13:49:27 2011 -0500
>> +++ b/xen/arch/x86/domain.c Tue May 03 13:59:37 2011 -0500
>> @@ -1578,6 +1578,7 @@
>> memcpy(stack_regs,&n->arch.user_regs, CTXT_SWITCH_STACK_BYTES);
>> if ( xsave_enabled(n)&& n->arch.xcr0 != get_xcr0() )
>> set_xcr0(n->arch.xcr0);
>> + vcpu_restore_fpu_eager(n);
> ... this call is unconditional, ...
>
>> n->arch.ctxt_switch_to(n);
>> }
>>
>> --- a/xen/arch/x86/i387.c Tue May 03 13:49:27 2011 -0500
>> +++ b/xen/arch/x86/i387.c Tue May 03 13:59:37 2011 -0500
>> @@ -160,10 +160,25 @@
>> /*******************************/
>> /* VCPU FPU Functions */
>> /*******************************/
>> +/* Restore FPU state whenever VCPU is schduled in. */
>> +void vcpu_restore_fpu_eager(struct vcpu *v)
>> +{
>> + ASSERT(!is_idle_vcpu(v));
>> +
>> + /* Avoid recursion */
>> + clts();
>> +
>> + /* save the nonlazy extended state which is not tracked by CR0.TS bit */
>> + if ( xsave_enabled(v) )
>> + fpu_xrstor(v, XSTATE_NONLAZY);
>> +
>> + stts();
> ... while here you do an unconditional clts followed by an xrstor only
> checking whether xsave is enabled (but not checking whether there's
> any non-lazy state to be restored) and, possibly the most expensive
> of all, an unconditional write of CR0.
>
> Jan
>
>> +}
>> +
>> /*
>> * Restore FPU state when #NM is triggered.
>> */
>> -void vcpu_restore_fpu(struct vcpu *v)
>> +void vcpu_restore_fpu_lazy(struct vcpu *v)
>> {
>> ASSERT(!is_idle_vcpu(v));
>>
>
>
next prev parent reply other threads:[~2011-05-04 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 20:17 [PATCH] FPU LWP 6/8: create lazy and non-lazy FPU restore functions Wei Huang
2011-05-04 7:09 ` Jan Beulich
2011-05-04 16:33 ` Wei Huang [this message]
2011-05-05 7:13 ` Jan Beulich
2011-05-05 21:41 ` Wei Huang
2011-05-06 7:49 ` Jan Beulich
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=4DC17FF3.5080706@amd.com \
--to=wei.huang2@amd.com \
--cc=JBeulich@novell.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.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.