| 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: <20140730105529.GB12448@amd.pavel.ucw.cz> Date: Wed, 30 Jul 2014 12:55:29 +0200 From: Pavel Machek <pavel@....cz> To: "Rafael J. Wysocki" <rjw@...ysocki.net> Cc: Linux PM list <linux-pm@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 3/3][update] PM / sleep: Introduce command line argument for sleep state enumeration Hi! > For this reason I'm considering changing the defaul behavior going forward (so > that "mem" is always present and means "the deepest sleep state available other > than hibernation"), but I don't want to do that in one go. Actually, I don't think that's good idea, at least on PC. The way to wake up from S3 is power button. The way to wake up from "echo freeze > state" is going to be different, right? If I disable S3 in the BIOS and get different result from "echo mem > state", that will be confusing. Similar (but less severe) problem is there with S1, as it will probably power down USB ports, etc. So for example if I have system with S1, learn to do "echo mem > state" and that it still charges my phone, then ACPI updates come and "echo mem > state" now puts it in S3 and not charging my phone -- that would be confusing. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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