From: Stephen Boyd <sboyd@codeaurora.org>
To: linux-kernel@vger.kernel.org
Cc: Russell King <linux@arm.linux.org.uk>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Optimized inlining for ARM
Date: Wed, 24 Nov 2010 15:56:58 -0800 [thread overview]
Message-ID: <1290643020-24558-1-git-send-email-sboyd@codeaurora.org> (raw)
I know that Ingo deliberately introduced this option as x86
specific, but I'd like to introduce this for ARM as well. To
avoid useless copy paste, I've made the option generic so
any arch can support it.
In an effort to make a tiny crash kernel this option can shave a
few kb off the crash kernel size. It also helps a regular kernel
have a smaller icache footprint which should be benficial.
This option isn't on by default so there is no harm in adding it
besides giving the user a potentially dangerous option to enable.
If it's really experimental we can add an "if EXPERIMENTAL" in the
second patch. In the end, I'd like to get a wider range of testing with
this feature enabled on ARM so I'm posting it here in hopes that
people can respond back with Tested-by tags (or Naks if it crashes their
system).
Stephen Boyd (2):
Make OPTIMIZE_INLINING a generic option
arm: add optimized inlining
arch/arm/Kconfig | 1 +
arch/x86/Kconfig | 4 +---
arch/x86/Kconfig.debug | 14 --------------
init/Kconfig | 18 ++++++++++++++++++
4 files changed, 20 insertions(+), 17 deletions(-)
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2010-11-24 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 23:56 Stephen Boyd [this message]
2010-11-24 23:56 ` [PATCH 1/2] Make OPTIMIZE_INLINING a generic option Stephen Boyd
2010-11-24 23:57 ` [PATCH 2/2] arm: add optimized inlining Stephen Boyd
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=1290643020-24558-1-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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