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] Re: [Qemu-devel] [PATCH 02/15] xen: Add xen_machine_fv

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [Qemu-devel] [PATCH 02/15] xen: Add xen_machine_fv
From: Kevin Wolf <kwolf@xxxxxxxxxx>
Date: Mon, 16 Aug 2010 16:13:58 +0200
Cc: Anthony Perard <anthony.perard@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "qemu-devel@xxxxxxxxxx" <qemu-devel@xxxxxxxxxx>
Delivery-date: Wed, 18 Aug 2010 07:58:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1008161454150.2545@kaball-desktop>
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>
References: <alpine.DEB.2.00.1008121244200.2545@kaball-desktop> <1281622202-3453-2-git-send-email-stefano.stabellini@xxxxxxxxxxxxx> <4C694054.8010600@xxxxxxxxxx> <alpine.DEB.2.00.1008161454150.2545@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100720 Fedora/3.0.6-1.fc12 Thunderbird/3.0.6
Am 16.08.2010 16:04, schrieb Stefano Stabellini:
> On Mon, 16 Aug 2010, Kevin Wolf wrote:
>> Am 12.08.2010 16:09, schrieb stefano.stabellini@xxxxxxxxxxxxx:
>>> From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
>>> Add the Xen FV (Fully Virtualized) machine to Qemu;
>>> this is groundwork to add Xen device model support in Qemu.
>>> Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
>>> Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
>> Why does this need its own machine type? Shouldn't an HVM machine really
>> look like a PC? And indeed most of this code looks like a (slightly
>> outdated) copy of pc_piix.c with !pci_enabled code paths removed.
> The main reason is that we need some xen specific initializations, as you can
> see from xen_init_fv.

Right, there are some more Xen specific things added later. However, the
main part of it is duplicated from pc_piix.c. I'm sure that with some
refactoring we could call these functions instead of copying and
modifying them. The problem with the latter is that they will inevitably
diverge even for changes that make sense for both.

I'm not even sure that the machine is the right place to do these Xen
specific initializations (expect for the Xen platform PCI device). As
far as I understand, the QEMUMachine is considered guest state whereas
most of these initializations concern host state.

> But considering that we have been asked to remove target-xen and that
> will cause a major refactoring of this series, xen_machine_fv could
> change significantly in the next iterations anyway...

Basically, the request to remove target-xen and my comment both aim in
the same direction, namely making Xen less special and integrate it
better in existing structures.


Xen-devel mailing list

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