From: Stratos Psomadakis <psomas@ece.ntua.gr>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
psomas@cslab.ntua.gr
Subject: Re: [PATCH 0/2] x86_32 cleanup: KERNEL_IMAGE_SIZE
Date: Mon, 28 Feb 2011 21:58:53 +0200 [thread overview]
Message-ID: <4D6BFE7D.9000907@ece.ntua.gr> (raw)
In-Reply-To: <1298841698-31823-1-git-send-email-psomas@cslab.ece.ntua.gr>
On 02/27/2011 11:21 PM, Stratos Psomadakis wrote:
> I noticed that KERNEL_IMAGE_SIZE is no longer used by x86_32 code
> (head_32.S no longer uses it for the initial kernel mapping).
>
> We can thus remove the assert from the vmlinux.lds.S file, and
> remove it completely for x86_32 code.
>
> Since head_32.S doesn't use it anymore, I can't find a reason
> why we should impose such a limit on the kernel image size
> (although a 512+MB kernel image isn't what one would call a realistic
> scenario :P)
>
> I think that a limit on the size of the image is imposed anyway
> by decompress_kernel()(if I understood correctly).
>
> I also updated the comments in head_32.S which still had references
> to KERNEL_IMAGE_SIZE.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
added cc, just in case anyone is interested
--
Stratos Psomadakis
<psomas@ece.ntua.gr>
prev parent reply other threads:[~2011-02-28 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 21:21 Stratos Psomadakis
2011-02-27 21:21 ` [PATCH 1/2] Remove KERNEL_IMAGE_SIZE for x86_32 code(no longer used) Stratos Psomadakis
2011-02-27 21:21 ` [PATCH 2/2] head_32.S: Update the comments for the initial kernel mapping(KERNEL_IMAGE_SIZE no " Stratos Psomadakis
2011-02-28 19:58 ` Stratos Psomadakis [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=4D6BFE7D.9000907@ece.ntua.gr \
--to=psomas@ece.ntua.gr \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=psomas@cslab.ntua.gr \
/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
Powered by JetHome