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-ppc-devel

[Xen-devel] RE: Linux PG_arch_1 conflict

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] RE: Linux PG_arch_1 conflict
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Mon, 13 Mar 2006 13:20:39 -0800
Cc: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, Hollis Blanchard <hollisb@xxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 13 Mar 2006 21:22:13 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcZE7uvVFMds7BEqQ6i1nQw9xZsC5wB9IOQw
Thread-topic: Linux PG_arch_1 conflict
> On 10 Mar 2006, at 21:11, Magenheimer, Dan (HP Labs Fort 
> Collins) wrote:
> 
> >> That thread seems to already have a solution. Has anybody 
> run it past
> >> Linux MM people? (Adding xen-devel to CC for greater exposure.)
> >
> > If by "solution" you mean that Keir could change Xenlinux to
> > add a new "PG_foreign" bit and change Xenlinux/x86 (and netback)
> > to use that bit rather than PG_arch_1, I agree.
> >
> > Comments, Keir (or others)?
> 
> Sounds like the proper fix. I'll leave it to Christian and others 
> involved in the Linux upstreaming effort to have the final word.

Comments, Christian (or others)?  Any chance this will get into
3.0.2?  Certainly it should be changed before attempting to push
the drivers upstream to Linux.

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

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