From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: x86: removing zImage support?
Date: Tue, 10 Mar 2009 18:47:00 -0700 [thread overview]
Message-ID: <49B71814.2090604@zytor.com> (raw)
In-Reply-To: <87fxhkg8qn.fsf@basil.nowhere.org>
Andi Kleen wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>
>> I'm thinking again about removing zImage support. An "allnoconfig"
>> kernel (with CONFIG_EMBEDDED=y to expose additional knobs, and
>> CONFIG_BINFMT_ELF=y so it can do anything at all) is currently 487K on
>> i386 -- very close to the upper limit of 512K for zImage.
>
> An alternative would be to do a concentrated effort to get rid of text bloat
> again. I bet it could be stripped down to much below that again by just
> attacking some low hanging fruit.
>
That wasn't exactly the point. The whole point is whether or not we can
reduce the complexity of the code by removing a mode which has few or no
users.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-03-11 1:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 0:20 x86: removing zImage support? H. Peter Anvin
2009-03-11 1:15 ` Andi Kleen
2009-03-11 1:47 ` H. Peter Anvin [this message]
2009-03-11 10:24 ` Ingo Molnar
2009-03-11 11:03 ` Thomas Gleixner
2009-03-11 14:14 ` Woody Suwalski
2009-03-11 17:03 ` H. Peter Anvin
2009-03-11 17:39 ` Ian Campbell
2009-03-11 18:02 ` H. Peter Anvin
2009-03-11 18:06 ` [tip:x86/setup] x86: remove zImage support H. Peter Anvin
2009-03-12 17:45 ` Paul Bolle
2009-03-12 19:25 ` H. Peter Anvin
2009-03-12 19:28 ` H. Peter Anvin
2009-03-12 19:57 ` [tip:x86/setup] x86: remove additional vestiges of the zImage/bzImage split H. Peter Anvin
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=49B71814.2090604@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--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