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] [Patch] Allow bitmasks with the badpage bootoption

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [Patch] Allow bitmasks with the badpage bootoption
From: "Erik Bosman" <ebosman@xxxxxxxxx>
Date: Wed, 5 Apr 2006 13:10:36 +0200
Delivery-date: Wed, 05 Apr 2006 04:10:53 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=P8aLnw8ojaZLrQIBACaFAoUProYCTJPRYfRRHdGpN2UfQI+DULvM//JIth/H6Q3YcheDq3TmMulwDgk+J/qKOpmHZdtVZ6KJDBx2ad7UG2VXSOnF2cqSMXDJNHDMGCSnSdrEinmOs5a+eoosvUV3Nf1U5vyOjvbRvfvCrJpZgEc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <49a267fe3eb03564486d6e7dbb21de83@xxxxxxxxxxxx>
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: <c535152a0604041022s35aaa391labac6cd1be94db39@xxxxxxxxxxxxxx> <49a267fe3eb03564486d6e7dbb21de83@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 4/5/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
>
> The masking scheme is unnecessarily restrictive. Why not just allow
> specification of inclusive ranges of pages? For example:
> badpage=0xa2000-0xa2fff,0x100-0x1ff,0x123-0x456
>
>   -- Keir
>

This was how I first implemented it for my machine, since it only requires
two ranges: badpage=0x2a000-0x2afff,0x3a000-0x3afff

But I thought a mask would be better since it resembles the way memory
usually breaks (not that I have much experience with this.)

On the other hand, ranges are much easier to understand.

I've attached my original patch.

Erik Bosman

Attachment: badpage-range.patch
Description: Text Data

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