From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hollis Blanchard Subject: Re: Linux PG_arch_1 conflict Date: Fri, 10 Mar 2006 14:59:10 -0600 Message-ID: <4411E89E.9090101@us.ibm.com> References: <516F50407E01324991DD6D07B0531AD59FF3C2@cacexc12.americas.cpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <516F50407E01324991DD6D07B0531AD59FF3C2@cacexc12.americas.cpqcorp.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Magenheimer, Dan (HP Labs Fort Collins)" Cc: xen-ppc-devel@lists.xensource.com, xen-devel@lists.xensource.com, xen-ia64-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Magenheimer, Dan (HP Labs Fort Collins) wrote: > See previous discussion at: > > http://lists.xensource.com/archives/html/xen-devel/2005-12/msg00238.html > > > The issue is that PG_arch_1 is reserved for arch-specific > usage, the paravirtualization changes for Xenlinux utilize > it (to mark foreign pages) because it was otherwise unused > in Linux/x86. But Xen is no longer an arch. > > Grep'ing for "PageForeign" in -sparse will show most (all?) > of the actual uses of it. Nearly all are in x86-specific > code. But one is in netback_init(). That thread seems to already have a solution. Has anybody run it past Linux MM people? (Adding xen-devel to CC for greater exposure.) -- Hollis Blanchard IBM Linux Technology Center