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 14:28:22 -0500
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 21 Jan 2008 11:28:50 -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=wRDZDDFhzuT1lVd547jVgJT3/CUo+9VwQtnv5wGZ9fk=; b=BnpQV/aTu41IzdGTnczodOy+Hf0Ivu106hzfeFhQ2v7pfl1XXtWoTsqiskhUntyDSwc9k1/Gzw1q3i0lw3a2MsEJunaPzpgZZP+5vo/tVM/zezG1+w4WPFRETbjTqgzlKXIiDi6Pnrebl8rhBHJpL3llngD96F0e+DTN1LbMwhc=
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=ZtJeLUxwgohYuv6J62NS9pCClEsOUMDTX/ecDcSBRkOYipIvmO+83d1g9QSaBarg6QawSzw1BhOTF5g9vTwL23K6fUDu7R7sF/aYsxJwfFpNDDBImJJjbrtNYDynsHALKdg3sU418rZh6Pd1GaSy/88Nz/A0Xn+gfmw98UiEmnI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3BA63D7.1B2F4%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: <1a74a8410801210541s21f23a6cgfb5c7daa21c1fbe5@xxxxxxxxxxxxxx> <C3BA63D7.1B2F4%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > 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).
>
> How is it wasteful? We could only do better if we assigned PCI resources in
> descending order of size (and hence alignment requirement). Which we *could*
> do, I suppose. Certainly the resource assignment code is going to get rather
> more exciting anyway, to fully support the dynamic PCI hole.

Pretty much that...the way it is now if the order in which BARs are
enumerated is such that the first BAR wants a small amount (say 1KB
and gets 0xF0000000-0xF00003FF) and then the second BAR wants a large
amout (say 64 MB and gets 0xF4000000-0xF7FFFFFF) then a there is a big
waste (0xF0000400-0xF3FFFFFF == ~64 MB).  In the various
configurations I was running almost as much PCI device address space
got wasted as assigned.

Thanks,
Dave

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