linux-kernel - Re: [PATCH x86] [15/16] Force __cpuinit on for CONFIG_PM without HOTPLUG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080114200126.GB9257@uranus.ravnborg.org>
Date:	Mon, 14 Jan 2008 21:01:26 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Andi Kleen <andi@...stfloor.org>,
	rjw@...k.pl, pavel@...e.cz, linux-kernel@...r.kernel.org
Subject: Re: [PATCH x86] [15/16] Force __cpuinit on for CONFIG_PM without HOTPLUG_CPU

On Mon, Jan 14, 2008 at 09:52:58PM +0200, Adrian Bunk wrote:
> On Mon, Jan 14, 2008 at 08:10:09PM +0100, Ingo Molnar wrote:
> > 
> > * Adrian Bunk <bunk@...nel.org> wrote:
> > 
> > > > for example, in current -git, could you tell me why this triggers:
> > > > 
> > > >  WARNING: vmlinux.o(.text+0x87e2a): Section mismatch: reference to 
> > > >           .init.text: (between 'process_zones' and 'setup_per_cpu_pageset')
> > > > 
> > > > and how to resolve it? I had a quick look and it was not obvious to me.
> > > 
> > > Please send the .config.
> > 
> > 'make allyesconfig' and disable CONFIG_HOTPLUG=y.
> 
> Works for me without the warning.
> 
> Wait, I remember something @#$%#@...!:
> 'make allyesconfig' on x86 became ambiguously.
> 
> If you have by chance a 64bit CPU that would explain why I didn't get it.
> 
> @Sam:
> Can you fix the bug that menuconfig does not let me enable CONFIG_64BIT?

make ARCH=x86_64 allyesconfig
will set CONFIG_64BIT for you - no?

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