[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Question about the dynamic sizing of the PCI hole


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Tom Rotenberg <tom.rotenberg@xxxxxxxxx>
  • Date: Mon, 25 May 2009 12:01:15 +0300
  • Delivery-date: Mon, 25 May 2009 02:01:45 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=weaLuZSpo6wLG+/E2xEV7TzKlIke2ecFUq0LGJhchcnZ68gqpzWrwMeVx/CAIYitgX yJQOxI7fld4kU5P9JtRkOT7EbG7jetqqsKQ4PVAyZkPTjPPirXWclN5ixKkMbBocvrDG /oEr9k8Hc8MpOY+tt8+JXlyjFZ7JYZbDZ6wtc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I am reviewing the code of the hvmloader from Xen 3.4, and i saw that in changeset 19021, there was a patch which added the ability to dynamically size the PCI hole. I have seen that this patch calculates the total memory size, but i failed to understand the following lines:

while ( (mmio_total > (pci_mem_end - pci_mem_start)) &&
            ((pci_mem_start << 1) != 0) )
        pci_mem_start <<= 1;

It looks as if the pci mem start will be increased if there isn't enough space for the PCI devices, although, as far as i understand, it should be decreased (so the PCI hole will be enlarged). So, shouldn't it be: "pci_mem_start >> = 1" ?

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.