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] Make memory hole for PCI Express bigger and prev

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch] Make memory hole for PCI Express bigger and prevent roll-over
From: "David Stone" <unclestoner@xxxxxxxxx>
Date: Mon, 21 Jan 2008 08:41:46 -0500
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 21 Jan 2008 05:42:11 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=3v4WzkfI1VLqo1I9lbLOUMjBRqapyF5ZY1TuDUaRAss=; b=YF/IGfeQM4fUqG78ZeaZUti1jrAXNk0fj7HvYweLFImUA6xlmsbt4TnIsqT8D2hqcsgYBD4ASFG6luuTJU4hjXIpUFyvYpH5LamOm8drE/9DkPNvhKKFnkK0YMZNO6VYeKmdIaC7tXwxhrCujadXepXzjj/cdqGkWp3a07waLGQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=F/t/OL1hf1h7Q4VmpE3Rdr7LZdQ2Qts2lUpGbTN0mqgsrOl9Z1Fic/NvDWwouMjuI1vbuaGEx7tI5UW0NBcCxW5GjgKKaVH0d6/AGv5it8mu31qHJ1C1JPMraqqlAlgjCqEMsCUnvdM6HeeXGs8Kbk+afm/A8V12kIkW7bqAAU4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3B6CB14.127F9%Keir.Fraser@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: <1a74a8410801181302k1923c547t3eb76edb3fc2fbc8@xxxxxxxxxxxxxx> <C3B6CB14.127F9%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Jan 18, 2008 4:31 PM, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> That's a very big hole. We should do this more dynamically.

OK fair enough.  As I said I have some code that dynamically modifies
the DSDT's AML.  I'll try to finish it up and submit it.

But in the meantime, will you take a patch (a subset of the patch I
just submitted) that keeps the hole as it is (starting at 0xF0000000)
but ensures it doesn't roll over to 0x00000000 in the Xen HVM BIOS?

Also should the hole used by the Xen HVM BIOS be limited to
0xF0000000-0xF4FFFFFF rather than 0xF00000000-0xFFFFFFFF?  Because:
  - The current DSDT specifies 0xF0000000-0xF4FFFFFF.
  - My understanding is that various other systems/components use
certain addresses at the top of 32-bit physical address space (like
maybe MSIs?).  So it would be bad to assign those physical addresses
to random PCI devices.
My only hesitation is that 0xF0000000-0xF4FFFFFF = 80Mb is smallish,
especially considering the wasteful algorithm the Xen HVM BIOS
currently uses to assign addresses (it can waste a lot of space).

Thanks,
Dave

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