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] Linux: PG_pinned vs. PG_foreign

To: Jan Beulich <jbeulich@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Linux: PG_pinned vs. PG_foreign
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Mon, 15 Jan 2007 10:10:59 +0000
Delivery-date: Mon, 15 Jan 2007 02:10:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45AB59A9.76E4.0078.0@xxxxxxxxxx>
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: Acc4jXPvsmaxQaSAEdukcwAX8io7RQ==
Thread-topic: [Xen-devel] Linux: PG_pinned vs. PG_foreign
User-agent: Microsoft-Entourage/11.2.5.060620
On 15/1/07 09:38, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

> Is it intentional that these two both use PG_arch_1? It seems at least risky
> to me... And if intended, it would certainly deserve a comment. (I was about
> to utilize PG_pinned for indicating pinned highmem-allocated PTEs when I
> realized this collision.)

There's no reason to have them use the same bit if there's a PG_arch_2
available. It was probbaly laziness on my part when I realised that (so far)
ForeignPage and Pinned are mutually exclusive.

 -- Keir


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

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