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: Wed, 04 Feb 2009 13:05:53 +1100 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: "Rafael J. Wysocki" <rjw@...k.pl> Cc: Jesse Barnes <jbarnes@...tuousgeek.org>, Linus Torvalds <torvalds@...ux-foundation.org>, pm list <linux-pm@...ts.linux-foundation.org>, LKML <linux-kernel@...r.kernel.org>, Linux PCI <linux-pci@...r.kernel.org> Subject: Re: [PATCH 7/7] PCI PM: Let the core be more careful with respect to drivers using new framework > For non-bridge devices without drivers the PCI PM core will disable > them and save their state on suspend. During resume, it will put > them into D0, if necessary, restore their state (early) and reenable > them. This is "without drivers" only or does it include devices that have a driver and no PM ops ? In the later case, the worry is that the driver will potentially still take shared interrupts after you have disabled the device. I know the normal disable path only disables bus mastering, which is a GOOD thing :-) but the pcibios hook might do more here ... I would recommend only doing that disabling in the "noirq" phase of suspend to avoid problems here. Do you see any reason that wouldn't work ? 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