From: Ingo Molnar <mingo@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Get rid of cpuinit?
Date: Tue, 28 May 2013 11:20:38 +0200 [thread overview]
Message-ID: <20130528092038.GC32068@gmail.com> (raw)
In-Reply-To: <20130520231203.GA21682@kroah.com>
* Greg KH <greg@kroah.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
next prev parent reply other threads:[~2013-05-28 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 22:35 Get rid of cpuinit? H. Peter Anvin
2013-05-20 23:12 ` Greg KH
2013-05-28 9:20 ` Ingo Molnar [this message]
2013-06-12 0:31 ` Paul Gortmaker
2013-06-12 0:56 ` Greg KH
2013-06-20 17:46 ` Status of __cpuinit removal Paul Gortmaker
2013-06-21 1:32 ` Greg KH
2013-06-23 10:15 ` Ingo Molnar
2013-05-22 21:04 ` Get rid of cpuinit? Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130528092038.GC32068@gmail.com \
--to=mingo@kernel.org \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).