 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] stub domain or "hyper thread" in xen
| To: | Xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] stub domain or "hyper thread" in xen |
| From: | "Ashish Bijlani" <ashish.bijlani@xxxxxxxxx> |
| Date: | Tue, 13 May 2008 23:40:52 -0400 |
| Delivery-date: | Tue, 13 May 2008 20:41:13 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=rlWCgfsPqjgLKeuTAzxf7AYc6xhvhG6xGund7zJzAWE=; b=VhbqK0zhk9tXkcC19Tx7Wvi8q+x5QXANwicLKCckfMVIKVKHmeNFXC9/OrFrmE+n/JLuMUAjeHDOhtGDB9NiQLmKWCfZldL9BxZLcGw7FmnV/iaCQO6jqhwrYwD/kHs8lygMwrZZZ2uRvINRJ5JHRERIalmuibeyVN76nKjplpo= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nswixuUZ+4g96qroOPCwsGSPu9EEWyBP+fBSURubBv0+gUGEB2ARsFPXi2zOL79bUADNNSIAkNQhloKMVGWhErOjKlLKAt4yEo0oMhkKNVCYx2XhhH7gW4yXv1KSt0XL3R0BQXQ56TudpP/mvkVaznaGWdvHuUn1sOUX3GCgyC8= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| 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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Hello, Why can't a guest domain be associated with a dom0 kernel thread (I call hyper thread) instead of a stub domain to do the I/O independently? I'm talking about introducing hyper threads (essentially dom0 kernel threads) below a guest domain's kernel threads and moving backend drivers and qemu device model functionality from dom0 to these "hyper threads" to do I/O independently.The idea is based on user-kernel thread model i.e. similar to the user-kernel thread architecture to do I/O through syscalls in an OS, there can be a guest kernel thread and a hyper thread association to do the I/O through hypercalls in an hypervisor based platform. -Ashish _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] PV driver build error on c/s 17630, Li, Haicheng |
|---|---|
| Next by Date: | [Xen-devel] netback.c, changxiaolin changxiaolin |
| Previous by Thread: | [Xen-devel] PV driver build error on c/s 17630, Li, Haicheng |
| Next by Thread: | Re: [Xen-devel] stub domain or "hyper thread" in xen, Samuel Thibault |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
