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] Re-design the architecture of Xen

Subject: Re: [Xen-devel] Re-design the architecture of Xen
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>
Date: Tue, 24 May 2011 16:42:53 +0200
Cc: henanwxr <henanwxr@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 24 May 2011 07:43:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110524142418.GF10926@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/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: <1306150777633-4418793.post@xxxxxxxxxxxxx> <20110524142418.GF10926@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Err, aren't you simply describing something similar to domDs, the Driver
domains that dom0 disaggregation plans already imagined?  I don't know
how far it is currently finished, but there is not so much redesign
needed: domUs frontends simply have to talk to domDs backends instead of
dom0 (not so big overhaul, mostly device paths in xenstore and details),
domDs being allowed to drive hardware directly independently from each
other (can be done through VT-d).


Xen-devel mailing list

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