| 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: <alpine.LFD.2.00.0902221500030.3111@localhost.localdomain> Date: Sun, 22 Feb 2009 15:02:31 -0800 (PST) From: Linus Torvalds <torvalds@...ux-foundation.org> To: "Eric W. Biederman" <ebiederm@...ssion.com> cc: "Rafael J. Wysocki" <rjw@...k.pl>, LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Jeremy Fitzhardinge <jeremy@...p.org>, pm list <linux-pm@...ts.linux-foundation.org>, Len Brown <lenb@...nel.org>, Jesse Barnes <jbarnes@...tuousgeek.org>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [RFC][PATCH 0/2] Rework disabling of interrupts during suspend-resume On Sun, 22 Feb 2009, Eric W. Biederman wrote: > > How does this sync with the ACPI requirement that the it's late suspend MUST > happen with irqs disabled? All the system device suspend and the actual CPU power-off still happens with CPU interrupts disabled. It's just that the regular two-phase device suspend code now runs first with interrupts enabled (the regular "->suspend()" callback), and then the second phase runs with the CPU still having interrupts on (and taking timer interrupts), but with the actual device interrupts disabled. Linus -- 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