From mboxrd@z Thu Jan  1 00:00:00 1970
From: George Dunlap <George.Dunlap@eu.citrix.com>
Subject: Re: [PATCH V4 3/7] libxl: add pvusb API
Date: Tue, 16 Jun 2015 12:45:37 +0100
Message-ID: <CAFLBxZa=dLBq=TSheKWR7FWshRwoftRYfr6ke5GzVtDvRZdM_A@mail.gmail.com>
References: <1433906441-3280-1-git-send-email-cyliu@suse.com>
	<1433906441-3280-4-git-send-email-cyliu@suse.com>
	<CAFLBxZbVXjj-VM4KLdhqBkpC0qSR_sy3mNnSZAJQJmHuo4ZC0Q@mail.gmail.com>
	<21887.64856.265751.921367@mariner.uk.xensource.com>
	<558000E5.9000803@suse.com>
	<21888.1058.681450.470806@mariner.uk.xensource.com>
	<5580079D.6070007@suse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <5580079D.6070007@suse.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Juergen Gross <jgross@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Ian Campbell <ian.campbell@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>, Chunyan Liu <cyliu@suse.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Jim Fehlig <jfehlig@suse.com>, Simon Cao <caobosimon@gmail.com>
List-Id: xen-devel@lists.xenproject.org

On Tue, Jun 16, 2015 at 12:25 PM, Juergen Gross <jgross@suse.com> wrote:
>>> qemu does support specifying a USB device via <vendorId>:<productId>,
>>> which is stable even across reboots, but unfortunately it isn't
>>> guaranteed to be unique (you can have plugged in two devices of the
>>> same type).
>>
>>
>> Indeed.  That would also be a thing we should allow people to do.
>>
>> AIUI some devices have serial numbers, which means you can distinguish
>> them ?
>
>
> Yes, they have. The question is whether those are different on multiple
> instances? With "lsusb" I've found a device with serial number
> 0123456789ABCD. Do you really believe I'm just lucky owning the one with
> such a nice serial number? ;-)

So it sounds like we're converging on "Allow multiple ways to specify
the interface", with at least the following fields:
- bus (int - 1,2,3, &c)
- port (string - 2.1.3, &c)
- address/devnum (int)
- vendorid (uint16_t)
- deviceid (uint16_t)

That solves the basic problem, because then the missing information
needed by the various paths can be looked up and added to the device
struct as needed.

 -George