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] IO emulation for HVM guest.

To: <xense-devel-request@xxxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] IO emulation for HVM guest.
From: "Praveen Kushwaha" <praveen.kushwaha@xxxxxxxxxxx>
Date: Wed, 4 Apr 2007 15:33:13 +0530
Delivery-date: Wed, 04 Apr 2007 03:04:27 -0700
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
Thread-index: Acd2oHUb1lbi27Z7SAaJxwIpD3EceA==
Thread-topic: IO emulation for HVM guest.


           Since the for HVM guest(full virtualization) , the emulated version of the all the IO devices are resides in dom0.

           Whenever HVM guest needs to access IO, VMExit happens(transition from guest to VMM). And from the VMM request goes to dom0, where emulated version of the IO device serves the request.


1. So the my question is that I want to put some hooks in the dom0, to capture the request. Is it possible to put hooks in dom0 for IO request from HVM guest?  

2. As per my knowledge there is qemu-dm which provides the emulated version of IO devices. Therefore What exactly the code I should look in xen for qemu-dm which handles the IO request?

3. what is the role of device channels in communication of IO from HVM guest?




Praveen Kushwaha




Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>