From: Sam Ravnborg <sam@ravnborg.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-arch <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <greg@kroah.com>
Subject: Re: Get rid of cpuinit?
Date: Wed, 22 May 2013 23:04:47 +0200 [thread overview]
Message-ID: <20130522210447.GA26123@merkur.ravnborg.org> (raw)
In-Reply-To: <519AA53F.1020107@zytor.com>
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.
If you grep for CPU_HOTPLUG in various defconfig files you will see that
it is only set in a few of these files (at least in arm/configs/).
I did not check it CPU_HOTPLUG would be set when
you actually used the config - but at least we need to pay attention
to the current usage.
Sam
prev parent reply other threads:[~2013-05-22 21:04 UTC|newest]
Thread overview: 10+ 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
2013-06-12 0:31 ` Paul Gortmaker
2013-06-12 0:56 ` Greg KH
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 ` Sam Ravnborg [this message]
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=20130522210447.GA26123@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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).