Date: Mon, 28 May 2007 15:26:25 +0200
From: Pavel Machek <pavel@ucw.cz>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.21.1] resume doesn't run suspended kernel?
Message-ID: <20070528132625.GQ18807@elf.ucw.cz>
References: <4658B7DD.3060309@tmr.com> <20070527211434.GG3989@ucw.cz> <465A4953.7030708@tmr.com> <465AD746.7090008@tmr.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <465AD746.7090008@tmr.com>
User-Agent: Mutt/1.5.11+cvs20060126
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1148
Lines: 26

Hi!

> >That's clear, I'll have to use xen or kvm or similar which restores 
> >the system as suspended. Thanks for the clarification of the limitations.
> >
> Sorry, I wrote that late at night and quickly. I should have said 
> "design decision" rather than "limitation," For systems which don't do 
> multiple kernels it's not an issue.
> 
> I certainly would not have made the same decision, but I didn't write 
> the code. It seems more robust to save everything than to try to 
> identify what has and hasn't changed in a modular kernel.

We rely on atomic copy routine not moving inside the kernel. Yes, it
would be possible to copy it to "known good" address and gain ability
to resume different kernels. Actually it should not be _that_ hard.

									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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/