| 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
| ||
|
Message-Id: <201110230010.37802.rjw@sisk.pl> Date: Sun, 23 Oct 2011 00:10:37 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Yinghai Lu <yinghai@...nel.org> Cc: Linux PCI <linux-pci@...r.kernel.org>, Jesse Barnes <jbarnes@...tuousgeek.org>, LKML <linux-kernel@...r.kernel.org>, Linux PM list <linux-pm@...r.kernel.org>, ACPI Devel Mailing List <linux-acpi@...r.kernel.org>, Matthew Garrett <mjg59@...f.ucam.org> Subject: Re: [PATCH] PCI / ACPI: Make acpiphp ignore root bridges using PCIe native hotplug On Saturday, October 22, 2011, Yinghai Lu wrote: > On Fri, Oct 21, 2011 at 3:43 PM, Rafael J. Wysocki <rjw@...k.pl> wrote: > > From: Rafael J. Wysocki <rjw@...k.pl> > > > > If the kernel has requested control of the PCIe native hotplug > > feature for a given root complex, the acpiphp driver should not try > > to handle that root complex and it should leave it to pciehp. > > Failing to do so causes problems to happen if acpiphp is loaded > > before pciehp on such systems. > > Should pciehp be built-in kernel instead of as a module? Well, perhaps. Still, though, if someone doesn't build pciehp and the control of the native PCIe hotplug is granted for a given root complex, acpiphp won't work anyway. Thanks, Rafael -- 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