public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* __init & __initdata during resume
@ 2004-10-22  4:06 Randy.Dunlap
  2004-10-22  7:54 ` Pavel Machek
  0 siblings, 1 reply; 2+ messages in thread
From: Randy.Dunlap @ 2004-10-22  4:06 UTC (permalink / raw)
  To: pavel, linux-kernel

Hi Pavel,

'make buildcheck' reports:
Error: ./arch/x86_64/ia32/syscall32.o .text refers to 0000000000000002
R_X86_64_PC32     .init.data+0x000000000000152b
Error: ./arch/x86_64/ia32/syscall32.o .text refers to 0000000000000017
R_X86_64_PC32     .init.data+0x000000000000152c


I'm looking at a recent (2 weeks) changeset:
[PATCH] Fix random crashes in x86-64 swsusp

http://linux.bkbits.net:8080/linux-2.5/cset@4166a52aYzzfOE3F63Kkb966K2Qz3g?nav=index.html|src/|src/arch|src/arch/x86_64|src/arch/x86_64/ia32|related/arch/x86_64/ia32/syscall32.c

in which this change was made:

-void __init syscall32_cpu_init(void)
+/* May not be __init: called during resume */
+void syscall32_cpu_init(void)

but syscall32_cpu_init() uses <use_sysenter>, which is:
static int use_sysenter __initdata = -1;

so the question is:  does that "__initdata" need to removed also?

--
~Randy


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: __init & __initdata during resume
  2004-10-22  4:06 __init & __initdata during resume Randy.Dunlap
@ 2004-10-22  7:54 ` Pavel Machek
  0 siblings, 0 replies; 2+ messages in thread
From: Pavel Machek @ 2004-10-22  7:54 UTC (permalink / raw)
  To: Randy.Dunlap; +Cc: linux-kernel

Hi!

> 'make buildcheck' reports:
> Error: ./arch/x86_64/ia32/syscall32.o .text refers to 0000000000000002
> R_X86_64_PC32     .init.data+0x000000000000152b
> Error: ./arch/x86_64/ia32/syscall32.o .text refers to 0000000000000017
> R_X86_64_PC32     .init.data+0x000000000000152c
> 
> 
> I'm looking at a recent (2 weeks) changeset:
> [PATCH] Fix random crashes in x86-64 swsusp
> 
> http://linux.bkbits.net:8080/linux-2.5/cset@4166a52aYzzfOE3F63Kkb966K2Qz3g?nav=index.html|src/|src/arch|src/arch/x86_64|src/arch/x86_64/ia32|related/arch/x86_64/ia32/syscall32.c
> 
> in which this change was made:
> 
> -void __init syscall32_cpu_init(void)
> +/* May not be __init: called during resume */
> +void syscall32_cpu_init(void)
> 
> but syscall32_cpu_init() uses <use_sysenter>, which is:
> static int use_sysenter __initdata = -1;
> 
> so the question is:  does that "__initdata" need to removed also?

Yes, I'm afraid that I overlooked that one.
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-10-22  8:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-22  4:06 __init & __initdata during resume Randy.Dunlap
2004-10-22  7:54 ` Pavel Machek

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox