All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Daniel Jacobowitz <drow@false.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Increase max -kernel size
Date: Tue, 27 Mar 2007 22:56:24 +0100	[thread overview]
Message-ID: <20070327215624.GA16825@networkno.de> (raw)
In-Reply-To: <20070327212511.GA25000@caradoc.them.org>

Daniel Jacobowitz wrote:
> On Tue, Mar 27, 2007 at 08:16:40PM +0100, Thiemo Seufer wrote:
> > Gwenole Beauchesne wrote:
> > > Hi,
> > > 
> > > The following patch increases max kernel size to 8 MB when qemu is invoked 
> > > with -kernel and -initrd. Otherwise, x86_64 kernel panics when loading the 
> > > initrd (e.g. <Cooker>/x86_64/isolinux/alt0/{vmlinuz,all.rdz}).
> > 
> > I would like a patch which adjusts the initrd load address dynamically,
> > depending on the kernel load size, instead of hardcoding just a
> > different magic number.
> 
> Note, that does not readily work - this is where we load the
> compressed kernel image and initrd, but what matters is the size it
> gets uncompressed to.

I think what matters is the space taken by (uncompressed and loaded)
kernel ALLOC segments. Everything above that should be ok to load a
ramdisk.

IOW, the ELF loader would need to return the topmost address it came
across, including .bss-like parts. The up-aligned value would become
the initrd load address.


Thiemo

  reply	other threads:[~2007-03-27 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 16:14 [Qemu-devel] [PATCH] Increase max -kernel size Gwenole Beauchesne
2007-03-27 16:32 ` Daniel Jacobowitz
2007-03-27 19:16 ` Thiemo Seufer
2007-03-27 21:25   ` Daniel Jacobowitz
2007-03-27 21:56     ` Thiemo Seufer [this message]
2007-03-27 22:27       ` Paul Brook
2007-03-27 23:35         ` Thiemo Seufer
2007-03-28  2:21           ` Daniel Jacobowitz
2007-03-28 14:00             ` Paul Brook
2007-03-31 15:41               ` Daniel Jacobowitz
2007-03-31 16:50                 ` Paul Brook

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=20070327215624.GA16825@networkno.de \
    --to=ths@networkno.de \
    --cc=drow@false.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.