WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [Patch 2/4] Refining Xsave/Xrestore support

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch 2/4] Refining Xsave/Xrestore support
From: Haitao Shan <maillists.shan@xxxxxxxxx>
Date: Thu, 28 Oct 2010 16:52:22 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Weidong Han <weidong.han@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Thu, 28 Oct 2010 01:52:55 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=c+B9KQxfLyEg33gMEQIfJJR8MyFG5HYPPF9lSr7Rxho=; b=JX6gYFHb6Ycv69AyeSLJ1F6Pp9gcvpP2opx76P4Pjz97yt7seCmx9vUoyQCpGt/V7S BjSolQDJli9HshJtPKSKvP16iVx7xT266a5PaWBEu3G/03d9MxyVHKd2HBCTAt/Intyr COn5tSjxtVA96MuqdUJKAdXHarNqn8gRGTRlE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=xxXgzUYLhENwnSmHDyGLt7hJMs8aQP8BetwrZfQbguNkOlpHq9N+/k7//ezkkj7DDN sb+Bjgiv3z3RJngYyMjwIRH0mQ4G84wWaGn/j7TVYkuI//przt26g1j0lJwBsObCbrfc Wk+O3ATOemY29PM/dYoQLhjf2I8XW2h0iiD/M=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4CC9507E020000780001FAA9@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTimWUuyHvZ06=2cRBhvw2fcfMzA5QAuJZJso7=gY@xxxxxxxxxxxxxx> <4CC81AD8020000780001F6BE@xxxxxxxxxxxxxxxxxx> <AANLkTim5DO3HQ_QCv-MK4auz7GDY3Mx+8g7MQJgsiVPS@xxxxxxxxxxxxxx> <4CC93F2B020000780001FA2E@xxxxxxxxxxxxxxxxxx> <AANLkTinNtX_DRr5NLxPtJz-Dtd4-wTF+LLMiiaLnd5C9@xxxxxxxxxxxxxx> <4CC9507E020000780001FAA9@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I have done a quick test on my box, setting XCR0 is around 130 tsc
cycles while reading XCR0 is around 80 tsc cycles.

Shan Haitao

2010/10/28 Jan Beulich <JBeulich@xxxxxxxxxx>:
>>>> On 28.10.10 at 09:52, Haitao Shan <maillists.shan@xxxxxxxxx> wrote:
>> Then I would prefer to write XCR0 unconditionally. Otherwise, I can
>> only refer to the approach for handling CR4 switches: reading CR4
>> first and checking whether there is a need to write actually.
>> But I don't think <a read to XCR0 plus a data comparison> can save any
>> compared with one unconditional write to XCR0.
>> Are you OK with this?
>
> Depends on the performance expectations of xsetbv and xgetbv
> (and its comparison to moves from/to control registers). At least
> there's no word in the documentation that xsetbv would be
> serializing. I would hope Intel could at least provide approximate
> numbers...
>
> Jan
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel