From: Pete Zaitcev <zaitcev@redhat.com>
To: harry <harry@hebutterworth.freeserve.co.uk>
Cc: xen-devel@lists.xensource.com,
linux-usb-devel@lists.sourceforge.net, zaitcev@redhat.com
Subject: Re: Error recovery in Xen's paravirtualizing USB driver for Linux
Date: Wed, 7 Dec 2005 15:00:29 -0800 [thread overview]
Message-ID: <20051207150029.48d3a125.zaitcev@redhat.com> (raw)
In-Reply-To: <1133980277.14981.65.camel@localhost.localdomain>
On Wed, 07 Dec 2005 18:31:17 +0000, harry <harry@hebutterworth.freeserve.co.uk> 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
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2005-12-07 23:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 18:31 Error recovery in Xen's paravirtualizing USB driver for Linux harry
2005-12-07 19:35 ` Alan Stern
2005-12-07 22:15 ` [linux-usb-devel] " Harry Butterworth
2005-12-08 15:20 ` Alan Stern
2005-12-08 15:59 ` [linux-usb-devel] " Harry Butterworth
2005-12-08 16:20 ` Alan Stern
2005-12-08 17:41 ` [linux-usb-devel] " Harry Butterworth
2005-12-08 18:53 ` Alan Stern
2005-12-08 22:24 ` [linux-usb-devel] " Harry Butterworth
2005-12-09 0:44 ` Greg KH
2005-12-09 11:03 ` [linux-usb-devel] " Harry Butterworth
2005-12-09 16:11 ` Alan Stern
2005-12-09 18:50 ` Harry Butterworth
2005-12-09 19:02 ` Alan Stern
2005-12-10 4:10 ` Greg KH
2005-12-07 23:00 ` Pete Zaitcev [this message]
2005-12-07 23:25 ` [linux-usb-devel] " Harry Butterworth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051207150029.48d3a125.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=harry@hebutterworth.freeserve.co.uk \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.