This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Using LinuxBIOS as virtual firmware

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Using LinuxBIOS as virtual firmware
From: "Yinghai Lu" <yinghai.lu@xxxxxxx>
Date: Sat, 15 Jul 2006 09:38:14 -0700
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Anthony Liguori <aliguori@xxxxxxxxxx>, Stefan Reinauer <stepan@xxxxxxxxxxxx>, Mark Williamson <mark.williamson@xxxxxxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Michael Loehr <MLOEHR@xxxxxxxxxx>, rminnich@xxxxxxxx
Delivery-date: Sat, 15 Jul 2006 09:38:38 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=OgnsrQU1cgufM55WA0KjxpTjWTTJBIDtsD72RTyNlQXj6s2ftpG2K39MTOKCxGSzqIl2NvBHeNf5vq6UWULX3siGQx/4YXRW1SXIE3W3sivvk7+xKrCF+mph/oSukoxhEai6SvaBzksdfFLTV6shyZSkS7RxmKmxRKfXNcWjTyA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <d3e7959e59ee3a8b9ef0915f6b69cbb9@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <6F7DA19D05F3CF40B890C7CA2DB13A4207004095@xxxxxxxxxxxxxxxxx> <d3e7959e59ee3a8b9ef0915f6b69cbb9@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
1. virtual firmware do the pci init ( including bus enumerating and
resource allocating)
2. virtual firmware create the acpi tables, mptable and irqtable
according to driver model and cpu accessing instead of let loader to
create thoese table.
3. So will have more clear boundary between driver model and vitutal firmware.

in the ioemu side, need to update the current code to AMD device.

Maybe the good way is using linuxbios+bochs and updating driver model
in qemu at the same time


Yinghai Lu

On 7/15/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

On 15 Jul 2006, at 01:40, Lu, Yinghai wrote:

> Is it a good way?
> Any comment?

It would be helpful to have a clearer explanation of the limitations of
the current firmware, the benefits of your new approach, and likely
effort and steps needed to get there. Also to compare that with the
difficulty of solving any current problems by simply patching the
current code base.

For example, if the only aim is to emulate AMD64 platforms more
accurately, maybe that is best done by evolving the current code. But
moving to LinuxBIOS might have other benefits too -- if so they need

Bear in mind also there's an increasing amount of work going into
hvmloader (e.g., SMBIOS patches) that will probably be impacted by a
move to a whole new firmware architecture.

  -- Keir

Xen-devel mailing list

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>