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] dom0 pvops crash

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] dom0 pvops crash
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Wed, 27 Jan 2010 11:34:54 -0800
Cc: Pasi Kärkkä, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 27 Jan 2010 11:35:17 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1264619930.2392.248.camel@xxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C783A22C.7599%keir.fraser@xxxxxxxxxxxxx> <4B5DF8E5.9040906@xxxxxxxx> <1264613173.16526.97718.camel@xxxxxxxxxxxxxxxxxxxxxx> <4B608AE2.1020501@xxxxxxxx> <1264619930.2392.248.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1
On 01/27/2010 11:18 AM, Ian Campbell wrote:
That's a thought.  It could be generally useful too; highpte should only
be used in extreme circumstances (to prevent ptes from filling most of
lowmem), not on every system with highmem.   IOW use a generic flag
rather than make it explicitly Xen-related, then we can set that flag.
I think this is the most plausible idea. Need to think about what
criteria would be used to set the flag on native, simply raw RAM size?
i.e. you wouldn't use HIGHPTE on a 4G system, even if CONFIG_HIGHPTE is
enabled, but where would the cut-off be?

Rather than a flag I guess I'd make a pte_gfp variable which could be
modified to suit.

Well, you could try heuristicing it up, but I suspect a simpler approach is just a variable which is enabled by command line and/or config option. HIGHPTE is an arch-independent concept, but the policy for defaulting it is arch-specific; on x86 it should almost always be off.

Or we could just put a big fat config dependency in.
I'd imagine that seemingly random "depends !XEN" would be unpopular
upstream.

I was thinking the other way around; Xen depends on !HIGHPTE. But a runtime switch would be just as good.

    J

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

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