From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754051AbbCBLjH (ORCPT ); Mon, 2 Mar 2015 06:39:07 -0500 Received: from smtp02.citrix.com ([66.165.176.63]:17076 "EHLO SMTP02.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751687AbbCBLjF (ORCPT ); Mon, 2 Mar 2015 06:39:05 -0500 X-IronPort-AV: E=Sophos;i="5.09,675,1418083200"; d="scan'208";a="240467562" Message-ID: <54F44BD5.1030008@citrix.com> Date: Mon, 2 Mar 2015 11:39:01 +0000 From: David Vrabel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0 MIME-Version: 1.0 To: Juergen Gross , , , , , , , , Subject: Re: [Xen-devel] [PATCH 3/4] usb: Introduce Xen pvUSB backend References: <1424957717-392-1-git-send-email-jgross@suse.com> <1424957717-392-4-git-send-email-jgross@suse.com> In-Reply-To: <1424957717-392-4-git-send-email-jgross@suse.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit X-DLP: MIA1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [Xen-devel] [PATCH 3/4] usb: Introduce Xen pvUSB backend Date: Mon, 2 Mar 2015 11:39:01 +0000 Message-ID: <54F44BD5.1030008@citrix.com> References: <1424957717-392-1-git-send-email-jgross@suse.com> <1424957717-392-4-git-send-email-jgross@suse.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <1424957717-392-4-git-send-email-jgross@suse.com> Sender: linux-kernel-owner@vger.kernel.org To: Juergen Gross , linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, konrad.wilk@oracle.com, david.vrabel@citrix.com, boris.ostrovsky@oracle.com, linux-usb@vger.kernel.org, gregkh@linuxfoundation.org, cyliu@suse.com List-Id: xen-devel@lists.xenproject.org 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