From: Joe Perches <joe@perches.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org,
linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: [PATCH 01/32] init.h: remove __cpuinit sections from the kernel
Date: Mon, 24 Jun 2013 12:51:18 -0700 [thread overview]
Message-ID: <1372103478.1245.23.camel@joe-AO722> (raw)
In-Reply-To: <1372102237-8757-2-git-send-email-paul.gortmaker@windriver.com>
On Mon, 2013-06-24 at 15:30 -0400, Paul Gortmaker wrote:
> The __cpuinit type of throwaway sections might have made sense
> some time ago when RAM was more constrained, but now the savings
> do not offset the cost and complications. For example, the fix in
> commit 5e427ec2d0 ("x86: Fix bit corruption at CPU resume time")
> is a good example of the nasty type of bugs that can be created
> with improper use of the various __init prefixes.
Hi Paul.
Could you please post the sizes of a generic kernel build
with and without this?
next parent reply other threads:[~2013-06-24 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1372102237-8757-1-git-send-email-paul.gortmaker@windriver.com>
[not found] ` <1372102237-8757-2-git-send-email-paul.gortmaker@windriver.com>
2013-06-24 19:51 ` Joe Perches [this message]
2013-06-24 22:10 ` [PATCH 01/32] init.h: remove __cpuinit sections from the kernel Joe Perches
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=1372103478.1245.23.camel@joe-AO722 \
--to=joe@perches.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).