linux-kernel - Re: Get rid of cpuinit?

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: <20130528092038.GC32068@gmail.com>
Date:	Tue, 28 May 2013 11:20:38 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Greg KH <greg@...ah.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	linux-arch <linux-arch@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Get rid of cpuinit?


* Greg KH <greg@...ah.com> wrote:

> On Mon, May 20, 2013 at 03:35:43PM -0700, H. Peter Anvin wrote:
> > We have gotten rid of devinit markup.  A recent patch of Linus' makes me
> > wonder if we similarly should get rid of cpuinit markup?
> > 
> > Just as with devices, the CPU hotplug machinery has been leveraged to
> > support a number of pieces of functionality such as suspend, which means
> > that on anything but the most embedded systems this functionality is
> > likely needed anyway.
> > 
> > On x86-64, for an "allyesconfig" build, the total amount of space in all
> > the .cpu* sections combined is 100K.
> 
> No objection from me on removing it, it just causes problems from what I
> can tell.

Indeed, there's a steady trickle of mis-annotated cpuinit sections, and no 
real tooling to make the annotations automatic or so in most of the cases. 
Manual simply does not seem to work in this case.

Thanks,

	Ingo
--
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/