From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH v7 0/3] xen, usb: support pvUSB frontend driver
Date: Tue, 23 Nov 2021 14:20:45 +0100 [thread overview]
Message-ID: <20211123132048.5335-1-jgross@suse.com> (raw)
This series adds XEN guest pvUSB support. With pvUSB it is possible to
use physical USB devices from a XEN domain.
Since V4 a lot of time (several years) has passed. This is a revived
attempt to get the frontend into the kernel.
The support consists of a frontend in form of a virtual hcd driver in
the unprivileged domU passing I/O-requests to the backend in a driver
domain (usually Dom0). The backend is not part of this patch series,
as it is supported via qemu.
The code is taken (and adapted) from the original pvUSB implementation
done for Linux 2.6 in 2008 by Fujitsu.
Normal operation of USB devices by adding and removing them dynamically
to/from a domain has been tested using various USB devices (USB 1.1,
2.0 and 3.0) using the qemu based backend.
Changes in V7:
- use SPDX header in usbif.h
Changes in V6:
- add SPDX line to driver
Changes in V5:
- added interface documentation to patch 1
- frontend no longer trusts backend to return only sane values
Changes in V4:
- remove sysfs file from frontend, as it violated the "one value per file"
rule and didn't serve any real purpose.
Changes in V3:
- move frontend to drivers/usb/host and rename it to xen-hcd.
- changed name prefixes in patch 1 to "xenusb" as requested by Greg
- use __u<n> types rather than uint<n>_t as requested by Greg
Changes in V2:
- removed backend, as it can be implemented in user land
- added some access macros and definitions to the pvUSB interface
description to make it independant from linux kernel USB internals
- adapted frontend to newer kernel version and use new pvUSB
interface macros
- set port status in one chunk as suggested by Oliver Neukum
Juergen Gross (3):
usb: Add Xen pvUSB protocol description
usb: Introduce Xen pvUSB frontend (xen hcd)
xen: add Xen pvUSB maintainer
MAINTAINERS | 8 +
drivers/usb/host/Kconfig | 11 +
drivers/usb/host/Makefile | 1 +
drivers/usb/host/xen-hcd.c | 1606 ++++++++++++++++++++++++++++++
include/xen/interface/io/usbif.h | 405 ++++++++
5 files changed, 2031 insertions(+)
create mode 100644 drivers/usb/host/xen-hcd.c
create mode 100644 include/xen/interface/io/usbif.h
--
2.26.2
next reply other threads:[~2021-11-23 13:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 13:20 Juergen Gross [this message]
2021-11-23 13:20 ` [PATCH v7 1/3] usb: Add Xen pvUSB protocol description Juergen Gross
2021-11-23 13:20 ` [PATCH v7 2/3] usb: Introduce Xen pvUSB frontend (xen hcd) Juergen Gross
2021-12-03 12:49 ` Greg Kroah-Hartman
2021-12-03 12:50 ` Juergen Gross
2021-12-13 13:58 ` Greg Kroah-Hartman
2021-11-23 13:20 ` [PATCH v7 3/3] xen: add Xen pvUSB maintainer Juergen Gross
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=20211123132048.5335-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).