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: Tue, 20 Nov 2007 10:33:06 +0900 From: Kenji Kaneshige <kaneshige.kenji@...fujitsu.com> To: Gary Hade <garyhade@...ibm.com>, Alex Chiang <achiang@...com> Cc: Matthew Wilcox <matthew@....cx>, gregkh@...e.de, kristen.c.accardi@...el.com, lenb@...nel.org, rick.jones2@...com, linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz, pcihpd-discuss@...ts.sourceforge.net, linux-acpi@...r.kernel.org Subject: Re: [PATCH 0/4, v3] Physical PCI slot objects Gary Hade ????????: > On Sat, Nov 17, 2007 at 11:29:54AM -0700, Alex Chiang wrote: >> Hi all, >> >> This is v3 of the pci_slot patch series. >> >> The major change is making the ACPI-PCI slot driver a Kconfig >> option, as per the recommendations of others (Gary, Kenji-san). > > Alex, What I was trying to suggest is a boot-time kernel option, > not a kernel configuration option. The basic idea is to give > the user (with a single binary kernel) the ability to include > your ACPI-PCI slot driver feature changes only when they are > really needed. In addition to reducing the number of > system/PCI hotplug driver combinations where your changes > would need to be validated, I believe would also help > alleviate other worries (e.g. Andi Kleen's memory consumption > concern). I believe this goal could also be achieved with the > kernel config option by making the pci_slot module runtime > loadable with the PCI hotplug drivers only visiting your new > code when the pci_slot driver is loaded, although I think this > would be more difficult to implement. > I agree to Gary very much. Thanks, Kenji Kaneshige - 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