All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>, Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.3?] multiboot: fix e801 memory map
Date: Thu, 29 Nov 2012 15:12:53 -0600	[thread overview]
Message-ID: <87boeg6rl6.fsf@codemonkey.ws> (raw)
In-Reply-To: <50B7BA3D.5010600@redhat.com>

Paolo Bonzini <pbonzini@redhat.com> writes:

> Il 29/11/2012 20:24, Alexander Graf ha scritto:
>>> > It is in hw/multiboot.c:
>>> > 
>>> >    stl_p(bootinfo + MBI_MEM_LOWER,   640);
>> You want to remove that one then.
>
> I wasn't sure of what happens if the multiboot option ROM is old.  Do we
> support that to any extent?

Option ROMs are migrated but reset after reboot.  I guess you could
migrate before the option ROM is executed but that seems extraordinarily
unlikely.

Regards,

Anthony Liguori

>
>> > Regarding the testcase, Xen will touch the EBDA without this patch and
>> > with http://permalink.gmane.org/gmane.comp.emulators.xen.devel/144855.
>> > However, SeaBIOS does not complain.
>>
>> I see :). Well, the patch is unintrusive enough for be ok for 1.3 IMHO.
>
> Actually it's relatively easy to see a failure with Xen and a need to
> PCI passthrough something with a bulky boot ROM; iSCSI or FC cards will
> do.  You'll need both the Xen patch above, and this patch to boot
> successfully.  Otherwise, it will fail to boot.
>
> Paolo

  reply	other threads:[~2012-11-29 21:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 17:11 [Qemu-devel] [PATCH 1.3?] multiboot: fix e801 memory map Paolo Bonzini
2012-11-29 17:11 ` [Qemu-devel] [PATCH] " Paolo Bonzini
2012-11-29 18:49 ` [Qemu-devel] [PATCH 1.3?] " Alexander Graf
2012-11-29 18:51 ` Alexander Graf
2012-11-29 19:21   ` Paolo Bonzini
2012-11-29 19:24     ` Alexander Graf
2012-11-29 19:40       ` Paolo Bonzini
2012-11-29 21:12         ` Anthony Liguori [this message]
2012-11-30 16:15 ` 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=87boeg6rl6.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=pbonzini@redhat.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 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.