All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Shakil k <shakilk1729@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen PVUSB work
Date: Mon, 19 Aug 2013 11:11:37 +0100	[thread overview]
Message-ID: <5211EF59.7030802@eu.citrix.com> (raw)
In-Reply-To: <CAGiEYNe2UDmom5Ptgj4bLs+uuhS0=LOXXDkrn6ZGnmTe3LmXGA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1862 bytes --]

On 16/08/13 23:34, Shakil k wrote:
>
> Hi George,
>
> Can you let me know the required work needed in the area of  libxl/xl 
> PVUSB also if you have any documents or suggestion, then please pass 
> on to me.
>

There are two things that need work, actually:

* Linux kernel side of the PVUSB.

There is a PVUSB implimentation in SuSE's "classic Xen" kernel that some 
people have been able to use, but there are reports that it can be a bit 
flaky.  There is no PVUSB kernel support in mainline Linux.  There was 
an initial port some time ago (Konrad can point you to the tree), but it 
needs to be rebased, fixed, and upstreamed.  If you have the time and 
inclination, this is probably the most critical part to getting PVUSB 
working for 4.4, as it's something the rest of us definitely don't have 
time to do.

* The toolstack side

Near the end of 4.3 we were developing a general interface for adding 
host USB devices.  The interface was designed to be able to support 
either HVM or PV guests.  It didn't make it in on time, but it's close 
to being done, and I fully expect that I can get it in for 4.4.  The 
patch series I was working on would have implemented only HVM guests, it 
should be fairly easy to extend for PV guests.

I probably won't have time to work on it for about a month or so; if the 
kernel side isn't your cup of tea, you'd be welcome to pick up that 
patch series and try to get it in shape for submission, then add the 
necessary PV bits.

Patch series here:

http://lists.xen.org/archives/html/xen-devel/2013-04/msg02012.html

Let me know if you do decide to go this route, and I can post the code 
which partially addresses those comments.

Information on steps required to initiate the PV USB connection given a 
working PVUSB front-end and back-end here:

http://www.neobiker.de/wiki/index.php?title=XEN-PVUSB

  -George


[-- Attachment #1.2: Type: text/html, Size: 2831 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-08-19 10:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 22:34 Xen PVUSB work Shakil k
2013-08-19 10:11 ` George Dunlap [this message]
2013-08-19 10:28   ` Pasi Kärkkäinen
2013-08-19 15:04     ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2014-04-14  6:17 Chunyan Liu
2014-04-14  9:05 ` Ian Campbell
2014-04-15  8:29   ` George Dunlap
2014-04-15  9:03     ` Ian Campbell
2014-04-15  8:28 ` George Dunlap

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=5211EF59.7030802@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=shakilk1729@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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.