| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 9 Dec 2013 11:20:55 -0800 From: Yinghai Lu <yinghai@...nel.org> To: Bjorn Helgaas <bhelgaas@...gle.com> Cc: Joseph Salisbury <joseph.salisbury@...onical.com>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "stable@...r.kernel.org" <stable@...r.kernel.org> Subject: Re: [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio On Mon, Dec 9, 2013 at 9:54 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote: > I don't see how the question of whether the host bridge has an > aperture above 4G is related to whether we should automatically > reassign resources. They seem orthogonal to me. No doubt it "fixes" > the current problem, but it doesn't make sense conceptually. the BIOS has problem to have two functions point to same position. During realloc first try: standard+two rom_bar+sriov will be fail at first as pci root bus does not have enough mmio range, later try will standard+two rom_bar it will fail too as root bus mmio range will still only fit standard+one rom_bar. My thoughts is limit use realloc auto in those systems that does not have mmio64 above 4g... so old system will never have to specify "pci=realloc=off" to disable it. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists