Re: [PATCH -mm] kexec jump -v9

From: Pavel Machek
Date: Wed Mar 12 2008 - 04:57:35 EST


Hi!

> > > > The features of this patch can be used for as follow:
> > > >
> > > > - A simple hibernation implementation without ACPI support. You can
> > > > kexec a hibernating kernel, save the memory image of original system
> > > > and shutdown the system. When resuming, you restore the memory image
> > > > of original system via ordinary kexec load then jump back.
> > > >
> > >
> > > The main usage of this functionality is for hibernation. I am not sure
> > > what has been the conclusion of previous discussions.
> > >
> > > Rafael/Pavel, does the approach of doing hibernation using a separate
> > > kernel holds promise?
> >
> > Its certainly "more traditional" method of doing hibernation than
> > tricks swsusp currently plays.
>
> What exactly are you referring to?

Well, traditionaly it is 'A saves B to disk' (like bootloader saves
kernel&userspace). In swsusp we have 'kernel saves itself'... which
works, too, but is pretty different design.

> > Now, I guess they are some difficulties, like ACPI integration, and
> > some basic drawbacks, like few seconds needed to boot second kernel
> > during suspend.
> >
> > ...OTOH this is probably only chance to eliminate freezer from
> > swsusp...
>
> Some facts:
>
> * There's no reason to think that we can't use this same mechanism for
> hibernation (the only difficulty seems to be the handling of devices used for
> saving the image).

Ok, at least kexec makes handling of suspend device easier.

> Moreover, if this had been the _only_ argument for the $subject functionality,
> I'd have been against it.

Fortunately its not the only one :-).

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