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

* 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, for resume to work? I mean, we'll have deeply 
kernel version dependent variables in RAM. Am i missing something 
obvious?

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64
  - From: "Rafael J. Wysocki" <[email protected]>

References:
- [PATCH] Hibernation: Document __save_processor_state() on x86-64
  - From: "Rafael J. Wysocki" <[email protected]>
- Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64
  - From: Ingo Molnar <[email protected]>
- Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64
  - From: "Rafael J. Wysocki" <[email protected]>

Prev by Date: Re: [PATCH] x86_64: clear IO_APIC before enabing apic error vector. v2
Next by Date: Re: [PATCH] x86: provide a DMI based port 0x80 I/O delay override
Previous by thread: Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64
Next by thread: Re: [PATCH] Hibernation: Document __save_processor_state() on x86-64
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]