linux-kernel - Re: [Xen-devel] [PATCH 3/4] usb: Introduce Xen pvUSB backend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <54F44BD5.1030008@citrix.com>
Date:	Mon, 2 Mar 2015 11:39:01 +0000
From:	David Vrabel <david.vrabel@...rix.com>
To:	Juergen Gross <jgross@...e.com>, <linux-kernel@...r.kernel.org>,
	<xen-devel@...ts.xensource.com>, <konrad.wilk@...cle.com>,
	<david.vrabel@...rix.com>, <boris.ostrovsky@...cle.com>,
	<linux-usb@...r.kernel.org>, <gregkh@...uxfoundation.org>,
	<cyliu@...e.com>
Subject: Re: [Xen-devel] [PATCH 3/4] usb: Introduce Xen pvUSB backend

On 26/02/15 13:35, Juergen Gross wrote:
> Introduces the Xen pvUSB backend. With pvUSB it is possible for a Xen
> domU to communicate with a USB device assigned to that domU. The
> communication is all done via the pvUSB backend in a driver domain
> (usually Dom0) which is owner of the physical device.

Why do we need a kernel usb backend instead of a user-space one using
libusb?

> Changes from the original version are:
> - port to upstream kernel
> - put all code in just one source file

?? I'm not sure that was an improvement.  The resulting single file is
too large IMO.

> - move module to appropriate location in kernel tree

drivers/xen/ is the correct location for this driver.

(I've not given the driver a detailed review yet.)

David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/