From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marek Marczykowski Subject: Re: [PATCH 1/2] libxl: Introduce functions to add and remove host USB devices to an HVM guest Date: Fri, 22 Mar 2013 17:16:02 +0100 Message-ID: <514C83C2.4050608@invisiblethingslab.com> References: <1363694970-17267-1-git-send-email-george.dunlap@eu.citrix.com> <514864C2.8060603@citrix.com> <51487078.5000608@eu.citrix.com> <5148A6A6.20400@citrix.com> <20809.59642.485413.982252@mariner.uk.xensource.com> <5149F6CD.2060900@eu.citrix.com> <20809.65387.657743.334820@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3746654793538694541==" Return-path: In-Reply-To: <20809.65387.657743.334820@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson Cc: George Dunlap , Roger Pau Monne , Ian Campbell , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============3746654793538694541== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig168C24DA6306288988476241" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig168C24DA6306288988476241 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 20.03.2013 19:26, Ian Jackson wrote: > George Dunlap writes ("Re: [Xen-devel] [PATCH 1/2] libxl: Introduce fun= ctions to add and remove host USB devices to an HVM guest"): >> There are some semantic differences that I think are important (or cou= ld=20 >> be important). One big one is that PVUSB appears to require the calle= r=20 >> to specify the virtual topology used, while with qemu it is not possib= le=20 >> to specify the virtual topology. This gives us a few options for a=20 >> unified interface: >=20 > The obvious answer to this is to make specifying the virtual topology > optional in the unified syntax. >=20 > (TBH I'm not sure why anyone would ever want to specify a particular > virtual topology. I'm sure most people would prefer just to let the > tools set something up.) Yes, specifying topology by hand (which basically means creating one USB = 1.1 bus and one USB 2.0 bus) is only inconvenience in PVUSB. It should be don= e automatically. >> PVUSB also (it seems) requires devices to be assigned to usbback befor= e=20 >> they can be given to guests. So in the pv case, device_add() would ha= ve=20 >> to do assign then attach, and device_del would have to do detach then = >> de-assign. That's probably not so bad. >=20 > I definitely think this should happen automatically. Indeed. This is one/two writes to sysfs. One possible difficulty: backend= can be in some domU instead of dom0, but then IMHO assigning device to usbbac= k can be left to the user. But important thing: interface needs to allow specify (optional) backend domain in addition to device itself (with default to dom0). Same as other= interfaces like block or network. --=20 Best Regards / Pozdrawiam, Marek Marczykowski Invisible Things Lab --------------enig168C24DA6306288988476241 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQEcBAEBAgAGBQJRTIPDAAoJENuP0xzK19cszysH/0gjggyxTKE8e9LHEP24Fjoc aRSh9W06A4AhNlpqTE6U7BZfle6zJzGdKKvHMAIm6f/qUUBfOeDiR7ctZXyEnNX3 EBe+9Pj3i68PsNjKwoOZ2HALdUUpBwnl2jIbFLLPAbRgn+w+nzDGK41czXt6KqLt lYTHtNsEZknEgK+R4SHEkbEvSHpIKM4ZcxY+W5mh13EtvMQoy+0vlL39DNn59XmW ioytYZZeJN+61QSSZmTjZV6ww8Vaqz1AUlErRd2EgQf+Pji4/9wAadenvEsBeaar wdDwGJdbX9+wZTgEIaz8cVsKZm2fXY1PrqXp4tyl9RK82G/NAFWDNjBrehOVSa0= =WQL9 -----END PGP SIGNATURE----- --------------enig168C24DA6306288988476241-- --===============3746654793538694541== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3746654793538694541==--