From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Increase max -kernel size
Date: Sat, 31 Mar 2007 17:50:30 +0100 [thread overview]
Message-ID: <200703311750.31241.paul@codesourcery.com> (raw)
In-Reply-To: <20070331154157.GA16877@caradoc.them.org>
> Like this? I can't reliably test that it fixes the problem - for some
> bizarre reason, I can now load kernels without this patch. But it
> looks right and I can load kernels with it, too.
Turns out there's a problem. qemu puts ACPI tables at the top of ram. We have
to be careful to avoid stomping on them.
Paul
prev parent reply other threads:[~2007-03-31 16:53 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
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 [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=200703311750.31241.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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 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 NNTP newsgroup(s).