From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Li Zhijian <lizhijian@cn.fujitsu.com>,
qemu-devel@nongnu.org, peter.maydell@linaro.org,
philip.li@intel.com, zhijianx.li@intel.com, philmd@redhat.com,
Richard Henderson <rth@twiddle.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Subject: Re: [Qemu-devel] [PATCH for-4.0 v4 4/4] i386: allow to load initrd below 4G for recent linux
Date: Tue, 8 Jan 2019 00:35:26 +0100 [thread overview]
Message-ID: <9f2b416c-2f29-b33c-0b0e-f6598df67c4e@redhat.com> (raw)
In-Reply-To: <20181227203118.GA19442@habkost.net>
On 27/12/18 21:31, Eduardo Habkost wrote:
> All that said, I miss one piece of information here: is
> XLF_CAN_BE_LOADED_ABOVE_4G really supposed to override
> header+0x22c? linux/Documentation/x86/boot.txt isn't clear about
> that. Is there any reference that can help us confirm this?
Linux has supported initrd up to 4 GB for a very long time (2007, long
before XLF_CAN_BE_LOADED_ABOVE_4G which was added in 2013), though it
only sets initrd_max to 2 GB to "work around bootloader bugs". So I
guess the flag can be taken as a hint that you can load at any address,
and perhaps could be renamed.
Paolo
next prev parent reply other threads:[~2019-01-07 23:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 2:32 [Qemu-devel] [PATCH for-4.0 v4 0/4] allow to load initrd below 4G for recent kernel Li Zhijian
2018-12-06 2:32 ` [Qemu-devel] [PATCH for-4.0 v4 1/4] unify len and addr type for memory/address APIs Li Zhijian
2019-01-07 10:04 ` Stefano Garzarella
2019-01-08 1:06 ` Li Zhijian
2018-12-06 2:32 ` [Qemu-devel] [PATCH for-4.0 v4 2/4] refactor load_image_size Li Zhijian
2018-12-21 16:12 ` Michael S. Tsirkin
2018-12-24 2:14 ` Li Zhijian
2019-01-07 10:33 ` Stefano Garzarella
2019-01-08 1:09 ` Li Zhijian
2018-12-06 2:32 ` [Qemu-devel] [PATCH for-4.0 v4 3/4] i386: import & use bootparam.h Li Zhijian
2018-12-21 16:04 ` Michael S. Tsirkin
2019-01-04 16:41 ` Stefano Garzarella
2019-01-08 1:11 ` Li Zhijian
2018-12-06 2:32 ` [Qemu-devel] [PATCH for-4.0 v4 4/4] i386: allow to load initrd below 4G for recent linux Li Zhijian
2018-12-21 16:10 ` Michael S. Tsirkin
2018-12-27 20:31 ` Eduardo Habkost
2018-12-28 7:20 ` Li Zhijian
2019-01-07 12:11 ` Stefano Garzarella
2019-01-09 6:22 ` Li Zhijian
2019-01-07 23:35 ` Paolo Bonzini [this message]
2018-12-21 1:37 ` [Qemu-devel] [PATCH for-4.0 v4 0/4] allow to load initrd below 4G for recent kernel Li Zhijian
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=9f2b416c-2f29-b33c-0b0e-f6598df67c4e@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lizhijian@cn.fujitsu.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philip.li@intel.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=zhijianx.li@intel.com \
/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).