Xen project Mailing List

Re: [Xen-devel] direct I/O access from domU

To: "Harry Butterworth" <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>

From: "ron minnich" <rminnich@xxxxxxxxx>

Date: Wed, 6 Dec 2006 09:09:47 -0700

Delivery-date: Wed, 06 Dec 2006 08:09:44 -0800

Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fbG5114+OTictmvKyXsmnuT0ASafPm1L0m6RlU8Ke8bRXDFrlncsveqnAxG0mI6w7X8fyv+ncWtakUnJtH20KUva7Rut/CI9PRLKxE19NW5Ydlef980wonq8xSZ42HrV4uHCIgvd1O7RelPFehUKzS5tQ7Lr5QB5q4wEbpc9bDY=

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 12/6/06, Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I did this for my USB driver testing for the PCI USB h/w.  I can't
remember the xen changeset which I used (it was xen 3 a few months ago)
but you could find out by searching the mailing list for the last time I
posted a USB split driver patch.

Thanks. I wish I knew why hiding was not working for me.

For the USB device it was fairly easy.  Hide it from the dom0 kernel,
grant it to the domU kernel make sure pci back and front are compiled
into the dom0/domU kernels respectively.

ok, I need to write pcifront for Plan 9.


Yenta is a PCI bridge though which rings alarm bells because the old
(Xen 2) driver domain support didn't work for bridges.

ah. That might be it then. Anyone know for sure? thanks ron _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.