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: Sun, 01 Nov 2015 07:47:04 +1100 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: David Miller <davem@...emloft.net>, yinghai@...nel.org Cc: khalid.aziz@...cle.com, bhelgaas@...gle.com, weiyang@...ux.vnet.ibm.com, linux@....tj, wangyijing@...wei.com, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v8 00/61] PCI: Resource allocation cleanup for v4.4 On Sat, 2015-10-31 at 14:51 -0400, David Miller wrote: > This is the way OF seems to work. > > It maps all of the ROMs essentially to the same address range, but > only enables one at a time as it inspects the ROMs and builds the > device tree during power-on. > > Then it makes sure all of them are disabled, and can therefore use > some of that address range for mapping other BARs. > > So if ROMs are disabled, you cannot put the address of such ROMs BAR > in the kernel's assigned PCI address resource list. > > I hope that is what you are doing? I've seen that sort of stuff on x86 as well. Possibly on POWER, I don't remember for sure. I've also seen the VBIOS of some cards manually remap the ROM BAR to cover BAR 0, extract stuff from it, then disable it. I think the ROM BAR must be treated as "special". It should probably done in a separate pass from all the other BARs of all the other adapters to be honest, and remapped if there's any conflict. Cheers, Ben -- 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