From mboxrd@z Thu Jan  1 00:00:00 1970
From: Cyrill Gorcunov <gorcunov@openvz.org>
Subject: Re: The way of mapping BIOS into the guest's address space
Date: Wed, 15 Feb 2012 14:12:34 +0400
Message-ID: <20120215101234.GJ1894@moon>
References: <CAO_0yfPuOOCwS95tk8f9VKF0Lci4WsQnEZU6Fy9LrOoOVswRhw@mail.gmail.com>
 <CAOJsxLEcZi8h9=njbq2c77Tw=xRACD-R+L0rOQjSsZcMoGnjhQ@mail.gmail.com>
 <20120214121342.GE1878@moon>
 <20120215040708.GA9262@morn.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Pekka Enberg <penberg@kernel.org>, Yang Bai <hamo.by@gmail.com>,
	kvm@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Sasha Levin <levinsasha928@gmail.com>,
	Asias He <asias.hejun@gmail.com>
To: Kevin O'Connor <kevin@koconnor.net>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-bk0-f46.google.com ([209.85.214.46]:64812 "EHLO
	mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756919Ab2BOKMj (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 15 Feb 2012 05:12:39 -0500
Received: by bkcjm19 with SMTP id jm19so754909bkc.19
        for <kvm@vger.kernel.org>; Wed, 15 Feb 2012 02:12:37 -0800 (PST)
Content-Disposition: inline
In-Reply-To: <20120215040708.GA9262@morn.localdomain>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.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