From: Jordan Justen <jljusten@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Bei Guan <gbtju85@gmail.com>, Gleb Natapov <gleb@redhat.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] How does the QEMU load the binary files bios.bin and vgabios-cirrus.bin?
Date: Thu, 7 Apr 2011 12:47:32 -0700 [thread overview]
Message-ID: <BANLkTimz7narUQ-Jihy=A+N+ovEkB5dYRQ@mail.gmail.com> (raw)
In-Reply-To: <4D9E0EAC.3020502@codemonkey.ws>
On Thu, Apr 7, 2011 at 12:21, Anthony Liguori <anthony@codemonkey.ws> wrote:
> QEMU does the leg work already to support SMM. It doesn't work with KVM
> because we treat SMM as ROM memory and trap read/write access.
>
> To make it work with KVM, you'd have to hack things around to switch the VGA
> space to RAM in order to the let the SMM code run. It's not impossible, but
> that's the main reason it doesn't Just Work.
Ah, SMM ASEG/BSEG? I think most recent firmware ignore that, use TSEG
(some higher up memory) and run in protected mode.
But, based on Gleb's other response, there are other, bigger issues as well...
-Jordan
next prev parent reply other threads:[~2011-04-07 19:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 8:22 [Qemu-devel] How does the QEMU load the binary files bios.bin and vgabios-cirrus.bin? Bei Guan
2011-04-07 13:28 ` Anthony Liguori
2011-04-07 15:31 ` Gleb Natapov
2011-04-07 15:42 ` Anthony Liguori
2011-04-07 15:51 ` Gleb Natapov
2011-04-07 16:08 ` Anthony Liguori
2011-04-07 18:18 ` Jordan Justen
2011-04-07 18:30 ` Gleb Natapov
2011-04-07 18:37 ` Anthony Liguori
2011-04-07 18:44 ` Gleb Natapov
2011-04-07 19:03 ` Jordan Justen
2011-04-07 19:16 ` Gleb Natapov
2011-04-07 19:24 ` Olivier Galibert
2011-04-07 19:58 ` Jordan Justen
2011-04-07 19:21 ` Anthony Liguori
2011-04-07 19:31 ` Gleb Natapov
2011-04-07 21:34 ` Anthony Liguori
2011-04-08 5:58 ` Gleb Natapov
2011-04-07 19:47 ` Jordan Justen [this message]
2011-04-07 17:30 ` malc
2011-04-07 17:07 ` Bei Guan
2011-04-07 17:31 ` Bei Guan
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='BANLkTimz7narUQ-Jihy=A+N+ovEkB5dYRQ@mail.gmail.com' \
--to=jljusten@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=gbtju85@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--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).