From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: Re-design the architecture of Xen
Date: Tue, 24 May 2011 16:42:53 +0200
Message-ID: <20110524144253.GE4916@const.bordeaux.inria.fr>
References: <1306150777633-4418793.post@n5.nabble.com>
	<20110524142418.GF10926@dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <20110524142418.GF10926@dumpdata.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
Cc: henanwxr <henanwxr@163.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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).

Samuel