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


[Xen-devel] [PATCH 00 of 11] RFC: hvmloader SeaBIOS integration

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 00 of 11] RFC: hvmloader SeaBIOS integration
From: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date: Tue, 05 Apr 2011 16:46:25 +0100
Cc: Ian Campbell <ian.campbell@xxxxxxxxxx>
Delivery-date: Tue, 05 Apr 2011 08:47:57 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mercurial-patchbomb/1.6.4
The following patchset is a WIP/RFC/vagueidea enabling the build of
two versions of hvmloader, the first using ROMBIOS and the second
using SeaBIOS.

This is achieved by compiling hvmloader.c multiple times which
required a certain amount of disentanglement and reworking to avoid
the need to compile other files more than once. The bulk of the series
consists of that work.

It's not clear to me that this is preferable to building a single
hvmloader which can pollinate a VM with either BIOS.

The final patch, which actually adds the SeaBIOS support, includes a
slew of ugly #ifdef'ery. Since it is not clear at the moment which of
this functionality is not needed with SeaBIOS and which is simply not
ready/working/tested yet I didn't put a great deal of effort into
refactoring that aspect.

It's a great shame that the choice of hvmloader binary was exposed to
users through the config file format. We'll have to cross that bridge
later I guess...

Xen-devel mailing list