Re: [Xen-devel] [PATCH] xen: cache current vcpu

To:	Christoph Egger <Christoph.Egger@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] [PATCH] xen: cache current vcpu
From:	Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date:	Mon, 29 Oct 2007 17:23:09 +0000
Delivery-date:	Mon, 29 Oct 2007 10:28:15 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<200710291643.45546.Christoph.Egger@xxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcgaUF/6nsIZuoZDEdyYhAAX8io7RQ==
Thread-topic:	[Xen-devel] [PATCH] xen: cache current vcpu
User-agent:	Microsoft-Entourage/11.3.6.070618

Gcc is quite capable of eliminating common subexpressions involving
current(), and I don't think this patch aids code readability (especially
the set_debugreg() change -- p==current means more to me than p==v).

 -- Keir

On 29/10/07 15:43, "Christoph Egger" <Christoph.Egger@xxxxxxx> wrote:

> 
> Hi!
> 
> Attached patch caches current vcpu.
> 
> Signed-off-by: Christoph Egger <Christoph.Egger@xxxxxxx>
> 

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

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] [PATCH] xen: cache current vcpu