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: <20080708193752.GD8694@ucw.cz>
Date:	Tue, 8 Jul 2008 21:37:53 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	Zhang Rui <rui.zhang@...el.com>
Cc:	linux-pm <linux-pm@...ts.linux-foundation.org>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] [RFC PATCH 0/4] save and restore ACPI NVS memory during hibernation

Hi!

> According to the ACPI spec, ACPI NVS memory region is required to
> be saved/restored by OS during hibernation.
> 
> Section 15.3.2 ACPI Spec 3.0b,
> "OSPM will call the _PTS control method some time before entering
> a sleeping state, to allow the platform???s AML code to update
> this memory image before entering the sleeping state.
> After the system awakes from an S4 state, OSPM will restore this
> memory area and call the _WAK control method to enable the BIOS
> to reclaim its memory image."
> 
> This patch set add the mechanism to save/restore ACPI NVS memory
> during hibernation.
> 
> Patch 01: call platform_begin before swsusp_shrink_memory.
> 	So that we can allocate enough pages for ACPI NVS memory
> 	before shrink the memory.

Why is it neccessary to allocate memory for a copy? We should be able
to save ACPI NVS area same way we are saving kernel pages, no?
-- 
(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

Powered by Openwall GNU/*/Linux Powered by OpenVZ