From: Anthony Liguori <anthony@codemonkey.ws>
To: Bei Guan <gbtju85@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] How does the QEMU load the binary files bios.bin and vgabios-cirrus.bin?
Date: Thu, 07 Apr 2011 08:28:37 -0500 [thread overview]
Message-ID: <4D9DBC05.8010400@codemonkey.ws> (raw)
In-Reply-To: <BANLkTiniHnWOAhhs4kz60dWOnVPO1x0GBw@mail.gmail.com>
On 04/07/2011 03:22 AM, Bei Guan wrote:
> Hi,
>
> I have some questions about the qemu's bios. How does the QEMU load
> the binary files bios.bin and vgabios-cirrus.bin? Which function or
> code file need I to pay more attention to?
>
> For the loading of vgabios-cirrus.bin and bios.bin, I just trace them
> into the same funciton rom_add_file() in hw/loader.c. Is it the
> right function, which loads the bioses?
>
> And then another question, how qemu give the control to bios when the
> bios file is loaded? Maybe this question is not in the scope of qemu,
> however, can you give me some cue point.
I had some stuff written up locally so I posted it to the wiki at
http://wiki.qemu.org/Documentation/Platforms/PC
The x86 architecture defines the initial state of the chip to have the
CS register have a base of 0xF000 and an IP of 0xFFF0. The result is
that the actual memory address of the first instruction falls at the end
of the BIOS ROM segment. This is the entry point to the BIOS.
The VGABIOS is treated like any other option ROM and is initialized
during option ROM scanning.
Regards,
Anthony Liguori
> Any reply are appreciated. Thanks.
>
> Gavin
>
>
>
>
next prev parent reply other threads:[~2011-04-07 13:29 UTC|newest]
Thread overview: 29+ 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 [this message]
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:37 ` Anthony Liguori
2011-04-07 18:44 ` Gleb Natapov
2011-04-07 18:44 ` Gleb Natapov
2011-04-07 19:03 ` Jordan Justen
2011-04-07 19:03 ` Jordan Justen
2011-04-07 19:16 ` Gleb Natapov
2011-04-07 19:16 ` Gleb Natapov
2011-04-07 19:24 ` Olivier Galibert
2011-04-07 19:24 ` Olivier Galibert
2011-04-07 19:58 ` Jordan Justen
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
2011-04-07 19:47 ` Jordan Justen
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=4D9DBC05.8010400@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=gbtju85@gmail.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.