[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] DomU-DomU Event Channel

If you assign a DomU "driver-domain", does that cause unnecessary communication overhead between your driver domain and domain0 as the native driver modules still reside in the domain0? or you will put your native driver in domU together with your BE driver?


----- Original Message ----- From: "Petersson, Mats" <Mats.Petersson@xxxxxxx> To: "Koripella Srinivas" <talkwithsrinivas@xxxxxxxxxxx>; <xen-devel@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, May 03, 2007 9:01 AM
Subject: RE: [Xen-devel] DomU-DomU Event Channel

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Koripella Srinivas
Sent: 03 May 2007 16:55
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] DomU-DomU Event Channel

I want to move the qemu emulation code running in domain0 and
move it to another domain for a particular device for a HVM
guest. As part of that i want to know if it is possible to
set up an event channel between 2 domU's.

I would have thought so, as you can assign a DomU "driver-domain" to be
the backend to another DomU - I take it that this would be roughly what
you're trying to do as well, except for a HVM-domain.

[This is pure speculation, based on my understanding of how domains talk
to each other combined with the functinality described by "xm



Xen-devel mailing list

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.