Hi.
I can answer a couple of the questions:
On Mon, 2004-01-19 at 16:35, Benjamin Herrenschmidt wrote:
> What is this file ? It's absolutely horrible....
It should contain the .S equivalent to the swsusp2.c file. It would be
best if swsusp2.c could simply be compiled, but it appears that it can't
at the moment on x86 (I need to learn x86 assembly so I can understand
why).
> >Index: arch/ppc/kernel/vmlinux.lds.S
> >===================================================================
> >--- arch/ppc/kernel/vmlinux.lds.S (revision 192)
> >+++ arch/ppc/kernel/vmlinux.lds.S (working copy)
> >@@ -72,6 +72,12 @@
> > CONSTRUCTORS
> > }
> >
> >+ . = ALIGN(4096);
> >+ __nosave_begin = .;
> >+ .data_nosave : { *(.data.nosave) }
> >+ . = ALIGN(4096);
> >+ __nosave_end = .;
> >+
> > . = ALIGN(32);
> > .data.cacheline_aligned : { *(.data.cacheline_aligned) }
>
> Why do you need the above for ?
That idea is to have a section that doesn't get replaced when we copy
the original kernel back. Thus, small amounts of data that suspend uses
or stores can be given the __nosave attribute. An example is the cpu
frequency value, which should match the boot kernel, not the value at
suspend time.
Regards,
Nigel
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
Attachment:
signature.asc
Description: This is a digitally signed message part