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: Sat, 22 Mar 2008 09:05:47 +1100 From: Nigel Cunningham <nigel@...el.suspend2.net> To: Alan Stern <stern@...land.harvard.edu> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Pavel Machek <pavel@....cz>, "Eric W. Biederman" <ebiederm@...ssion.com>, Kexec Mailing List <kexec@...ts.infradead.org>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>, linux-pm@...ts.linux-foundation.org, Vivek Goyal <vgoyal@...hat.com>, Len Brown <len.brown@...el.com> Subject: Re: [linux-pm] [PATCH -mm] kexec jump -v9 Hi. On Thu, 2008-03-20 at 20:52 -0400, Alan Stern wrote: > For an S5 hibernation, the interpreter state within the image is wrong. > The image kernel needs to have the interpreter state from the boot > kernel -- I don't know if this is possible. It's possible. 1) When hibernating, allocate a page (or pages if one isn't enough) for the data to end up in after the atomic restore. 2) Put the location(s) in the image header. 3) At resume time, allocate an equivalent number of extra 'safe' pages and set up extra pbes for the atomic restore to copy data from the extra pages to the ones allocated when hibernating. 4) At the appropriate point in time, copy the NVS data to the extra 'safe' pages allocated in step 3. The data will then be available to the resumed kernel post-resume. I've been using this method to pass data from the boot kernel to the resumed kernel for a while now. (I'm using it for I/O speed statistics and state preservation). Regards, Nigel -- 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