Re: The way of mapping BIOS into the guest's address space

[Cyrill Gorcunov <gorcunov@openvz.org>]

On Tue, Feb 14, 2012 at 11:07:08PM -0500, Kevin O'Connor wrote:
...
> > hardware. Maybe we could poke someone from KVM camp for a hint?
> 
> SeaBIOS has two ways to be deployed - first is to copy the image to
> the top of the first 1MB (eg, 0xe0000-0xfffff) and jump to
> 0xf000:0xfff0 in 16bit mode.  The second way is to use the SeaBIOS elf
> and deploy into memory (according to the elf memory map) and jump to
> SeaBIOS in 32bit mode (according to the elf entry point).
> 
> SeaBIOS doesn't really need to be in the top 4G of ram.  SeaBIOS does
> expect to have normal PC hardware devices (eg, a PIC), though many
> hardware devices can be compiled out via its kconfig interface.  The
> more interesting challenge will likely be in communicating critical
> pieces of information (eg, total memory size) into SeaBIOS.
> 
> The SeaBIOS mailing list (seabios@seabios.org) is probably a better
> location for technical seabios questions.
> 

Hi Kevin, thanks for pointing. Yes, providing info back to seabios
to setup mttr and such (so seabios would recognize them) is
most challeging I think.

	Cyrill