| 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: Thu, 27 Dec 2007 10:41:29 +0100 From: Oliver Neukum <oliver@...kum.org> To: Pavel Machek <pavel@....cz> Cc: kernel list <linux-kernel@...r.kernel.org>, Linux-pm mailing list <linux-pm@...ts.osdl.org>, "Rafael J. Wysocki" <rjw@...k.pl> Subject: Re: [RFC] sleepy linux Am Mittwoch, 26. Dezember 2007 21:32:58 schrieb Pavel Machek: > ... I also don't need to call any suspend() routines, because all the > drivers are already suspended, right? Well, you have a number of devices which cannot do runtime pm. They can do suspend/resume with the whole system. For them these operations mean saving/restoring state. So for these devices implementing autosuspend makes no sense. They would sensibly do only idle/busy detection. > And yes, I want device activity to prevent s2ram. If user is burning > CD, machine should not sleep. If user is actively typing, machine In these cases the devices involved should report themselves busy, shouldn't they? > should not sleep. My vision is: screen saver tells kernel keyboard > need not be very responsive, at that point keyboard driver can > autosuspend the keyboard, and if that was the last device, whole > system sleeps. We lack a notion of telling devices that they are opened only for detecting wakeups. Currently a driver has to assume that an opened device has to be fully functional. Regards Oliver -- 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