[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: USB virt

I ported the FE and BE to a new interdomain communication interface and
the USB driver is mostly complete (the claim port interface needs to be
fixed up and there is a state machine which needs to be fixed).

I'm about halfway through the implementation of the interdomain
communication interface.

I defined a new interdomain communication interface because I wanted to
decouple the driver from changes in the underlying infrastructure so I
didn't have to rewrite it a fourth time for the next flavour of xenbus.

Also, I think the interdomain communication API I've written ought to be
generally useful and save a lot of code if people reuse it in other

I've attached a patch of the current code.  It compiles until it gets to
some undefined references for functions I've not implemented yet.

I'm currently working on the endpoint object.  This is going to be
implemented in three layers: xenid_gnttab_channel, xenidc_xbgt_channel
and a third layer not yet complete.  The current endpoint implementation
is crufty because I'm in the middle of factoring out the code into those
three layers.

Feedback on the code would be welcome.


On Mon, 2005-10-24 at 16:56 +0100, Mark Williamson wrote:
> Hi Harry,
> Could you tell me what the status was on this?  Is there any chance of 
> getting 
> a snapshot of the code online somewhere?
> Regarding the implementation, it sounds like you've done a good job making it 
> work with lots of USB devices.  I am curious as to why you're defining a new 
> interdomain communications interface, though - XenBus is meant to be there 
> for the forseeable future ... ?
> Thanks very much,
> Mark

Attachment: latest-usb-patch
Description: Text Data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.