On Wed, Jul 16, 2014 at 6:00 PM, Chuck Tuffli <ctuffli@xxxxxxxxx> wrote: > On Wed, Jul 16, 2014 at 4:47 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote: > ... >> in the tree: >> 80:03.0 ==> 96:00.0 ==> 97:08.0 ==> 98:00.0 ==> 99:00.0 ==> 9a:00.0 >> ==> 9b:15.0 >> >> only 97:08.0 and 99:00.0 is hotplug+. >> >> and kernel will honor BIOS set value at first, and realloc will only work on >> unassigned/invalid assigned BARs. and hpmem_size will be only treated at >> optional size even on hotplug slots. > > Does this mean the only time the kernel will re-allocate the BARs and > use hpmemsize is if they have the value 0x0? If so, does realloc have > any limitations with respect to where in the tree the invalid BAR > exists? In my example, could realloc fix 80:03.0? 9b:15.0? the problem is 9b:15.0 is not hotplugable, when a5:00.0 is not inserted into the slot, realloc will not pre-reserve range for 9b:15.0. > If the BIOS doesn't allocate enough memory mapped IO resources for > devices, it sounds like the kernel can't really fix this problem, > right? Yes. You need to fix BIOS at first. So it will be final products or just development prototype? Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
