From: "Serge E. Hallyn" <serge@hallyn.com>
To: Scott Moser <smoser@ubuntu.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix multiboot loading if load_end_addr == 0 (fwd)
Date: Tue, 20 Mar 2012 15:04:09 +0000 [thread overview]
Message-ID: <20120320150408.GA8348@mail.hallyn.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1203181344200.4638@brickies>
Quoting Scott Moser (smoser@ubuntu.com):
> Re-sending to qemu-devel. I'd originally sent this to kvm mailing list.
>
>
> ---------- Forwarded message ----------
> Date: Sat, 17 Mar 2012 00:08:06
> From: Scott Moser <smoser@ubuntu.com>
> To: kvm@vger.kernel.org
> Subject: [PATCH] fix multiboot loading if load_end_addr == 0
>
> The previous code did not treat the case where load_end_addr was 0
> specially. The multiboot specification says the following:
> * load_end_addr
> Contains the physical address of the end of the data segment.
> (load_end_addr - load_addr) specifies how much data to load. This
> implies that the text and data segments must be consecutive in the
> OS image; this is true for existing a.out executable formats. If
> this field is zero, the boot loader assumes that the text and data
> segments occupy the whole OS image file.
>
> This was raised initially as launchpad bug
> https://bugs.launchpad.net/qemu/+bug/957622
>
Tested-by: Serge Hallyn <serge.hallyn@canonical.com>
> diff --git a/hw/multiboot.c b/hw/multiboot.c
> index b4484a3..b1e04c5 100644
> --- a/hw/multiboot.c
> +++ b/hw/multiboot.c
> @@ -202,10 +202,16 @@ int load_multiboot(void *fw_cfg,
> uint32_t mh_bss_end_addr = ldl_p(header+i+24);
> mh_load_addr = ldl_p(header+i+16);
> uint32_t mb_kernel_text_offset = i - (mh_header_addr - mh_load_addr);
> - uint32_t mb_load_size = mh_load_end_addr - mh_load_addr;
> -
> + uint32_t mb_load_size = 0;
> mh_entry_addr = ldl_p(header+i+28);
> - mb_kernel_size = mh_bss_end_addr - mh_load_addr;
> +
> + if (mh_load_end_addr) {
> + mb_kernel_size = mh_bss_end_addr - mh_load_addr;
> + mb_load_size = mh_load_end_addr - mh_load_addr;
> + } else {
> + mb_kernel_size = kernel_file_size - mb_kernel_text_offset;
> + mb_load_size = mb_kernel_size;
> + }
>
> /* Valid if mh_flags sets MULTIBOOT_HEADER_HAS_VBE.
> uint32_t mh_mode_type = ldl_p(header+i+32);
next prev parent reply other threads:[~2012-03-20 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-18 17:45 [Qemu-devel] [PATCH] fix multiboot loading if load_end_addr == 0 (fwd) Scott Moser
2012-03-20 15:04 ` Serge E. Hallyn [this message]
2012-03-26 19:17 ` Anthony Liguori
2012-03-26 19:27 ` [Qemu-devel] [PATCH] fix multiboot loading if load_end_addr == 0 Scott Moser
2012-05-26 22:17 ` Kevin Wolf
2012-05-27 0:52 ` Anthony Liguori
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=20120320150408.GA8348@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=qemu-devel@nongnu.org \
--cc=smoser@ubuntu.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).