| 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: <201105142053.34920.oliver@neukum.org> Date: Sat, 14 May 2011 20:53:34 +0200 From: Oliver Neukum <oliver@...kum.org> To: linux-pm@...ts.linux-foundation.org Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Raffaele Recalcati <lamiaposta71@...il.com>, davinci-linux-open-source@...ux.davincidsp.com, linux-kernel@...r.kernel.org Subject: Re: [linux-pm] pm loss development Am Donnerstag, 12. Mai 2011, 21:27:44 schrieb Rafael J. Wysocki: > On Thursday, May 12, 2011, Raffaele Recalcati wrote: > > What happen normally in runtime pm implementation is that every devices > > are switched off and are enabled only when needed. > > In our case instead we have a completely functional embedded system and, > > when an asyncrhonous event appear, we have only some tens milliseconds > > before the actual power failure takes place. > > This patchset add a support in order to switch off not vital part of the system, > > in order to allow the board to survive longer. > > This allow the possibility to save important data. > > OK, so first, who decides what parts of the system are vital and what aren't? If you know that power is failing in a few miliseconds, only stuff that can lead to data corruption is vital. In that timeframe you can't even flush buffers. 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