qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] multiboot: Fix module loading and setting of	mmap
Date: Wed, 18 Nov 2009 15:33:10 +0100	[thread overview]
Message-ID: <4B0405A6.5080706@suse.de> (raw)
In-Reply-To: <20091118140207.GB31670@os.inf.tu-dresden.de>

Adam Lackorzynski wrote:
> Hi,
>
> I need to following to fix multiboot booting for me.
>
> Should linuxboot.bin and multiboot.bin end up in pc-bios instead of
> pc-bios/optionrom?
>
>
> Signed-off-by: Adam Lackorzynski <adam@os.inf.tu-dresden.de>
> ---
>  hw/pc.c                       |    4 ++--
>  pc-bios/optionrom/multiboot.S |    5 ++++-
>  2 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/hw/pc.c b/hw/pc.c
> index 7c791c4..1c8f95c 100644
> --- a/hw/pc.c
> +++ b/hw/pc.c
> @@ -661,7 +661,7 @@ static int load_multiboot(void *fw_cfg,
>  
>              /* append module data at the end of last module */
>              mb_kernel_data = qemu_realloc(mb_kernel_data,
> -                                          mh_load_addr - mb_mod_end);
> +                                          mb_mod_end - mh_load_addr);
>   

Right. I wonder why it worked for me before?

>              load_image(initrd_filename,
>                         mb_kernel_data + mb_mod_start - mh_load_addr);
>  
> @@ -720,7 +720,7 @@ static int load_multiboot(void *fw_cfg,
>      fw_cfg_add_bytes(fw_cfg, FW_CFG_INITRD_DATA, mb_bootinfo_data,
>                       sizeof(bootinfo));
>  
> -    option_rom[nb_option_roms] = "multiboot.bin";
> +    option_rom[nb_option_roms] = "optionrom/multiboot.bin";
>   

This is wrong. The .bin file should be in pc-bios. It just doesn't get
copied over as part of the build process, but instead relies on the
committer to make sure the binary is updated on every source change.

>      nb_option_roms++;
>  
>      return 1; /* yes, we are multiboot */
> diff --git a/pc-bios/optionrom/multiboot.S b/pc-bios/optionrom/multiboot.S
> index be5c9fc..9131837 100644
> --- a/pc-bios/optionrom/multiboot.S
> +++ b/pc-bios/optionrom/multiboot.S
> @@ -62,6 +62,9 @@ run_multiboot:
>  	add		%eax, %ebx
>  	movl		%ebx, %gs:GS_GDT_DESC + 2
>  
> +	xor		%eax, %eax
> +	mov		%eax, %es
> +
>   

Ack. %es could be in any state here.

>  	/* Read the bootinfo struct into RAM */
>  	read_fw_blob(FW_CFG_INITRD)
>  
> @@ -71,7 +74,7 @@ run_multiboot:
>  	mov		%ax, %fs
>  
>  	/* ES = mmap_addr */
> -	mov		%eax, %fs:0x48
> +	mov 		%fs:48, %eax
>   

Right...


Thanks for catching those!

Alex

  reply	other threads:[~2009-11-18 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 14:02 [Qemu-devel] [PATCH] multiboot: Fix module loading and setting of mmap Adam Lackorzynski
2009-11-18 14:33 ` Alexander Graf [this message]
2009-11-18 14:53   ` Adam Lackorzynski
2009-11-18 15:12     ` Alexander Graf
2009-11-18 14:35 ` 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=4B0405A6.5080706@suse.de \
    --to=agraf@suse.de \
    --cc=adam@os.inf.tu-dresden.de \
    --cc=aliguori@us.ibm.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).