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

[Xen-devel] Re: [patch 2/8] Implement always-locked bit ops, for memory

To: Andi Kleen <ak@xxxxxxx>
Subject: [Xen-devel] Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
From: Christoph Lameter <clameter@xxxxxxx>
Date: Wed, 2 Aug 2006 21:25:18 -0700 (PDT)
Cc: Zachary Amsden <zach@xxxxxxxxxx>, akpm@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Pratt <ian.pratt@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx
Delivery-date: Thu, 03 Aug 2006 03:19:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200608030555.34569.ak@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>
References: <20060803002510.634721860@xxxxxxxxxxxxx> <44D14ECC.3080600@xxxxxxxxxx> <Pine.LNX.4.64.0608021821350.26404@xxxxxxxxxxxxxxxxxxxxxxxxx> <200608030555.34569.ak@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 3 Aug 2006, Andi Kleen wrote:

> On Thursday 03 August 2006 03:25, Christoph Lameter wrote:
> 
> > Good idea. This will also make it easier to support this special 
> > functionality. And it will avoid use in contexts where these are
> > not necessary.
> 
> I think it's a bad idea. We don't want lots of architecture ifdefs
> in some Xen specific file

Thats not how it would be done. We would do this with
architecture specific xen files and a default in asm-generic.


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

<Prev in Thread] Current Thread [Next in Thread>