From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>, Amos Kong <akong@redhat.com>
Cc: seabios@seabios.org, lersek@redhat.com,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] about [SeaBIOS PATCH] Try to hard-reboot on rerun of post even on emulators.
Date: Tue, 21 Apr 2015 10:30:00 +0200 [thread overview]
Message-ID: <55360A88.5050406@redhat.com> (raw)
In-Reply-To: <20150421002924.GA7259@morn.localdomain>
On 21/04/2015 02:29, Kevin O'Connor wrote:
> On a typical x86 machine, the BIOS image is located in read-only
> memory at 0xffff0000. The chipsets typically also support shadowing
> that image to ram (or as a read-only copy) at 0xf0000. However,
> neither qemu nor kvm fully support all the shadowing capabilities of a
> typical x86 chipset. So, seabios will copy itself from the image at
> 0xffff0000 to ram at 0xf0000. Unfortunately, kvm had a bug where the
> resulting ram image at 0xf0000 was actually mapped to the same ram at
> 0xffff0000 and changes to the memory copy at 0xf0000 would also change
> the copy at 0xffff0000. This made it impossible for reboots to
> redeploy the original pristine copy of seabios.
Nowadays QEMU and KVM can emulate this correctly, but any version of
QEMU before the introduction of the memory API (before 1.1 roughly) was
not able to support this.
Paolo
next prev parent reply other threads:[~2015-04-21 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 23:31 [Qemu-devel] about [SeaBIOS PATCH] Try to hard-reboot on rerun of post even on emulators Amos Kong
2015-04-21 0:29 ` Kevin O'Connor
2015-04-21 8:30 ` Paolo Bonzini [this message]
2015-04-21 8:37 ` Laszlo Ersek
2015-04-21 15:06 ` Kevin O'Connor
2015-04-21 16:54 ` Laszlo Ersek
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=55360A88.5050406@redhat.com \
--to=pbonzini@redhat.com \
--cc=akong@redhat.com \
--cc=kevin@koconnor.net \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).