Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64 (rev. 2)

2008-01-02 Thread Ingo Molnar
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > Document the fact that __save_processor_state() has to save all > > > CPU registers referred to by the kernel in case a different kernel > > > is used to load and restore a hibernation image containing it. > > > > > > Sigend-off-by: Rafael J

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64 (rev. 2)

2008-01-01 Thread Rafael J. Wysocki
On Wednesday, 2 of January 2008, Pavel Machek wrote: > On Sun 2007-12-30 23:13:51, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > > > Document the fact that __save_processor_state() has to save all CPU > > registers referred to by the kernel in case a different kernel

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64 (rev. 2)

2008-01-01 Thread Pavel Machek
On Sun 2007-12-30 23:13:51, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > Document the fact that __save_processor_state() has to save all CPU > registers referred to by the kernel in case a different kernel is > used to load and restore a hibernation image containing i

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-31 Thread Rafael J. Wysocki
On Monday, 31 of December 2007, Ingo Molnar wrote: > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > > ok, just to make sure we are talking about the same thing. Do you > > > mean we can restore an image saved by v2.6.12 into v2.6.24? I.e. a > > > 2.6.24 kernel will be able to run a 2.6.

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-31 Thread Ingo Molnar
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > ok, just to make sure we are talking about the same thing. Do you > > mean we can restore an image saved by v2.6.12 into v2.6.24? I.e. a > > 2.6.24 kernel will be able to run a 2.6.12 kernel's hibernation > > image, with all the kernel interna

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-31 Thread Torsten Kaiser
On Dec 30, 2007 10:57 PM, Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > > what's exactly in the hibernation image? Dirty data i suppose > > > > No, everything, including the kernel code, page tables etc. :-) > > > > > - but what about kernel-interna

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Rafael J. Wysocki
On Sunday, 30 of December 2007, Ingo Molnar wrote: > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > > what's exactly in the hibernation image? Dirty data i suppose > > > > No, everything, including the kernel code, page tables etc. :-) > > > > > - but what about kernel-internal pages. W

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Ingo Molnar
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > what's exactly in the hibernation image? Dirty data i suppose > > No, everything, including the kernel code, page tables etc. :-) > > > - but what about kernel-internal pages. What if we go from SLAB to > > SLUB? What if the size of a structur

[PATCH] Hibernation: Document __save_processor_state() on x86-64 (rev. 2)

2007-12-30 Thread Rafael J. Wysocki
From: Rafael J. Wysocki <[EMAIL PROTECTED]> Document the fact that __save_processor_state() has to save all CPU registers referred to by the kernel in case a different kernel is used to load and restore a hibernation image containing it. Sigend-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]> ---

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Rafael J. Wysocki
On Sunday, 30 of December 2007, Ingo Molnar wrote: > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > > how different can it be, for resume to work? I mean, we'll have > > > deeply kernel version dependent variables in RAM. Am i missing > > > something obvious? > > > > On x86-64 it can b

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Ingo Molnar
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > how different can it be, for resume to work? I mean, we'll have > > deeply kernel version dependent variables in RAM. Am i missing > > something obvious? > > On x86-64 it can be almost totally different (by restoring a > hibernation image we

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Rafael J. Wysocki
On Sunday, 30 of December 2007, Ingo Molnar wrote: > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > > But i'm wondering - are we really ever resuming to a different > > > kernel version, for this to be an issue? > > > > The boot kernel may be different from the kernel within the image,

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Ingo Molnar
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > But i'm wondering - are we really ever resuming to a different > > kernel version, for this to be an issue? > > The boot kernel may be different from the kernel within the image, if > that's what you're asking for. how different can it be, fo

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Rafael J. Wysocki
On Sunday, 30 of December 2007, Ingo Molnar wrote: > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > > > Document the fact that __save_processor_state() has to save all CPU > > registers referred to by the kernel in case a different kernel

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Pavel Machek
On Sun 2007-12-30 14:30:07, Rafael J. Wysocki wrote: > On Sunday, 30 of December 2007, Pavel Machek wrote: > > Hi! > > > > > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > > > > > Document the fact that __save_processor_state() has to save all CPU > > > registers referred to by the kernel in cas

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Ingo Molnar
* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > Document the fact that __save_processor_state() has to save all CPU > registers referred to by the kernel in case a different kernel is used > to load and restore a hibernation image containing it.

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-30 Thread Rafael J. Wysocki
On Sunday, 30 of December 2007, Pavel Machek wrote: > Hi! > > > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > > > Document the fact that __save_processor_state() has to save all CPU > > registers referred to by the kernel in case a different kernel is > > used to load and restore a hibernation

Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-29 Thread Pavel Machek
Hi! > From: Rafael J. Wysocki <[EMAIL PROTECTED]> > > Document the fact that __save_processor_state() has to save all CPU > registers referred to by the kernel in case a different kernel is > used to load and restore a hibernation image containing it. > Sigend-off-by: Rafael J. Wysocki <[EMAIL

[PATCH] Hibernation: Document __save_processor_state() on x86-64

2007-12-28 Thread Rafael J. Wysocki
From: Rafael J. Wysocki <[EMAIL PROTECTED]> Document the fact that __save_processor_state() has to save all CPU registers referred to by the kernel in case a different kernel is used to load and restore a hibernation image containing it. Sigend-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]> ---