WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: Error recovery in Xen's paravirtualizing USB driver for

To: harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: Error recovery in Xen's paravirtualizing USB driver for Linux
From: Pete Zaitcev <zaitcev@xxxxxxxxxx>
Date: Wed, 7 Dec 2005 15:00:29 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx, zaitcev@xxxxxxxxxx
Delivery-date: Thu, 08 Dec 2005 11:55:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1133980277.14981.65.camel@xxxxxxxxxxxxxxxxxxxxx>
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>
Organization: Red Hat, Inc.
References: <1133980277.14981.65.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 07 Dec 2005 18:31:17 +0000, harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 
wrote:

>     This 'USB split driver' has a 'front-end' in the Linux kernel
> running in a guest domain of the hypervisor and a 'back-end' in the
> Linux kernel running in a device driver domain (usually the special
> privilidged domain 0).

Why don't you just let guest 0 to own the controller? This is what
the guest 0 is for, as far as I know.

If you create special stub drivers in the hypervisor, you might as
well create virtual USB controllers for nonzero guests.

> o - The back-end uses usb_register to register itself as a driver
> matching all USB IDs so it gets probed for every USB device that is
> connected.  When a USB device is probed for a configured port, the
> driver claims all the interfaces for the device.

Ewww! Ewww!

You are just going to hit all the difficulties the vmware guy hit,
perhaps minus the size limitation in usbfs since you are bypassing it.

I would expect that the scheme you're proposing were employed to
let non-zero guests to drive some virtualized devices, but not for
the guest zero.

-- Pete

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel