linux-kernel - Re: [2.6.21.1] resume doesn't run suspended kernel?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070529112952.GA23046@elf.ucw.cz>
Date:	Tue, 29 May 2007 13:29:53 +0200
From:	Pavel Machek <pavel@....cz>
To:	Nigel Cunningham <nigel@...el.suspend2.net>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Bill Davidsen <davidsen@....com>,
	Linux Kernel M/L <linux-kernel@...r.kernel.org>
Subject: Re: [2.6.21.1] resume doesn't run suspended kernel?

Hi!

> > Yup.  Don't we do something like this for the (ACPI-based) suspend to RAM
> > already?
> 
> Yeah, I was thinking about this overnight too. It should be doable. In
> addition to what we already do, I think you'd want:
> 
> - to copy the assembly to do the copying to a safe page;
> - to put the location of the cpu state that was saved in the image
> header so that it can be used after the data is copied back;

...alternatively, we can just rely on copy routine (and its data) not
changing frequently.

> - to copy the nosave data to a 'safe' page.
> 
> What else?

page directories need to be on a safe place, too.
								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/