Nigel Cunningham wrote:

Hi Nick et al.

On Tue, 2005-08-09 at 14:59, Nick Piggin wrote:

quoted

quoted

Changing the e820 code so it sets PageNosave instead of PageReserved,
along with a couple of modifications in swsusp itself should get rid of
the swsusp dependency.

That would work for swsusp, but there are other users that want to
know if a struct page is valid ram (eg. ioremap), so in that case
swsusp would not be able to mess with the flag.

Um. Mess with which flag? I guess you mean Reserved. I was saying that

Mess with PageNosave (if that is what we used to denote a struct page
not pointing to valid RAM).

Ie. when swsusp allocates its save map (or whatever it calls it), setting
PageNosave would make other parts of the kernel think the area is not
valid ram.

In other words - we can't combine swsusp's PageNosave with our mythical
PageValidRAM.

imaging Reserved going away, so for the short term I'd be meaning making
the e820 set both Nosave and Reserved for those pages (which is what the
Suspend2 patches do so as to play nicely with swsusp - I don't use
Reserved at all).

In the short term, PageReserved can stay around - swsusp does still
work if I hadn't made that clear.

By the way - how does swsusp2 handle this problem if not using
PageReserved?


-- 
SUSE Labs, Novell Inc.

Send instant messages to your online friends http://au.messenger.yahoo.com 
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>