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] USB Xen Summit status summary

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] USB Xen Summit status summary
From: Nivedita Singhvi <nsnix@xxxxxxxxxxx>
Date: Wed, 01 Feb 2006 08:28:06 -0800
Delivery-date: Wed, 01 Feb 2006 16:38:05 +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
User-agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
Since Harry Butterworth, who's been working on the USB
virtualization couldn't attend the Xen Summit, I sat in
for him and am providing this summary:

Here were the options under consideration:

1. Xen includes current patch Harry had put out, which
   includes his IDC API.
2. Harry puts out a simpler USB driver without his IDC
   API, written directly to the current Xen bus/store API,
   and reducing to only features deemed needed for Xen,
   see if that will be accepted into tree.
3. Examine USBoverIP patches (currently in -mm tree)
   and see if those provide all the functionality we
4. Throw away everything and have someone else rewrite
   from scratch.

There was a brief discussion at the Client (Graphics,
USB...) session on USB. Ewan and several community folks
were present. Opinions expressed:

- Harry's IDC code and current code will not make it
  into tree as is [consensus]
- IDC piece very unlikely to be accepted into Linux mainline,
  hence should not go into Xen tree
- API code is orthogonal to USB driver piece, should be
  a seperate patch/discussion [consensus]
- Best option is (2), rewrite code to leaner, simpler
  USB driver with minimal functionality, and get that into
- Noone in session had looked at USBoverIp patches
- There were some good ideas in the IDC API that needed
  to be discussed/incorporated in Xen

Other input/questions received:
- Need to get USB community input
- What were the issues that were left? Are they resolved?
  If so, what's the current working state of the patch?
- Keir: rewrite to a simpler driver without the IDC API
  as the xenbus/store stuff is pretty baked into Xen now,
  might want to do some cleanups in this area.
- Ian: look at USBoverIP, tried it and it seems to
  work, but not sure if that's the right solution

Current Issues/Design questions:
- Harry's code supports back/front module load/unload
  (useful during development, if nothing else).
- Harry's code is not written to Ewan's last common
  code pullout API
- What other code functionality can be dropped in order
  to make it smaller?

[All misrepresentations and errors are mine, I'm operating
 from memory and on occasion what I heard over the crowd noise :)]

Hope that initiates the necessary conversation on this...


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>