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 0 of 3] Patches when Linux Xen drivers are modules.

To: xen-devel@xxxxxxxxxxxxxxxxxxx, keir.fraser@xxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0 of 3] Patches when Linux Xen drivers are modules.
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 22 Dec 2009 16:48:55 -0000
Cc: konrad.wilk@xxxxxxxxxx
Delivery-date: Tue, 22 Dec 2009 11:24:04 -0800
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.3
Keir, and Xen-devel mailing list,

Attached are three patches that help Dom0 and DomU respectivly when
both Xen backend and Xen-frontend drivers are modules.

a) The first two are to make 'xen-detect' be more useful in initrd
/initramfs situations. It can return 1 when running in PV context,
2 in HVM context, and 0 if Xen has not been detected. Also there are
three arguments: -P, -H, and -N, which will print a string value
if we are in either PV, HVM or no Xen context, respectivly.

An example user of this patch to Fedora's dracut: 

b) The xend init script is to load backend drivers if they
are modules.

Xen-devel mailing list