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] USB virt 2.6 split driver patch series

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] USB virt 2.6 split driver patch series
From: harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 21 Nov 2005 13:18:24 +0000
Delivery-date: Mon, 21 Nov 2005 13:18:09 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
I'm about to post a series of 17 patches which implement the xenidc
interdomain communications code and the USB split driver built on the
xenidc code.

These patches have been tested against today's unstable for the i386
build and can be successfully used to create a filesystem on and mount a
USB key.

Currently the code requires swiotlb=force and there are a few issues
which need to be addressed:

o - The USB protocol requires stalling the URB queue during error
conditions.  This isn't done correctly yet which makes the code unsafe
for write access during error recovery.  The 2.4 code had this problem
as well I only discovered it recently.

o - The USB-specific part of the interdomain protocol is using polling
for device discovery which is inefficient.  This is the same strategy as
the 2.4 code.

o - The resource pools are currently only allocating the minimum
resources required to avoid deadlock so performance will be resource
constrained.  This can be fixed either by implementing a larger static
resource allocation or improving the buffer_resource_provider to
implement a dynamic shared resource pool.  Either is fairly easy.

o - I've reformatted all the code to the kernel coding style using
Lindent and not attempted to improve it after that.  Some of the
formatting needs to be improved.

Now that it's basically working, if possible, I'd like to get the code
into the tree and work on it there.

Any feedback on the patches, particularly on what it's going to take to
get the code into the tree, would be most welcome.

Harry.


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