From: Juergen Gross <jgross@suse.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Chunyan Liu <cyliu@suse.com>, Jim Fehlig <jfehlig@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH V7 6/7] xl: add usb-assignable-list command
Date: Wed, 7 Oct 2015 16:47:43 +0200 [thread overview]
Message-ID: <5615308F.3090105@suse.com> (raw)
In-Reply-To: <CAFLBxZZ5zgRZzAd974N+1-WB7w+9xrDhpaxv-_M3M=vH9W7GYA@mail.gmail.com>
On 10/07/2015 04:35 PM, George Dunlap wrote:
> On Wed, Oct 7, 2015 at 3:26 PM, Juergen Gross <jgross@suse.com> wrote:
>> On 10/07/2015 04:05 PM, Ian Campbell wrote:
>>>
>>> On Wed, 2015-10-07 at 15:54 +0200, Juergen Gross wrote:
>>>
>>>> Hmm, technically all unassigned USB-devices are usable from Dom0. So why
>>>> not list them there.
>>>
>>>
>>> I think you'd at least want to distinguish USB devices available to dom0
>>> as
>>> via a PCI host controller from those which are available via pvusb.
>>
>>
>> Yeah, the non-pvusb devices should be listed as "assignable" if they
>> are handled by a driver domain.
>>
>>> This also doesn't quite work when driver domains are in the picture.
>>
>>
>> --host does?
>>
>> TBH: driver domains seem to be a reason to not support the --host
>> option. So the options are --all or no special option. I'm still
>> fine with both.
>
> I think the idea is that --host doesn't pretend to. But yes, if we
> made it clear which devices were *assigned* to dom0 from another VM,
> and which were *available from* dom0 to be assigned, then actually
> that could be extended at some point in the future to include devices
> available *from* driver domains.
>
> Alternately, perhaps we should just have
> # xl usb-available [domain]
Would work for me.
Wait, wasn't there a similar command suggested? Something like
"xl usb-assignable-list"? ;-)
> Which will tell you the usb devices available to be assigned from that
> domain; or all available usb devices from all driver domains. And of
> course for the time being it only works on domain 0, but future
> functionality could implement it for driver domains as well.
>
>> BTW: Do Xen concepts allow to assign a USB-device via pvUSB from a
>> driver domain to Dom0?
>
> Sure, why not?
With driver domains the picture is becoming more complicated.
The main question now is: What is the real purpose of "xl usb-list"?
Should it list the devices which are assigned to a domain, or should it
list the devices which are usable by a domain (probably attributed
whether the device is assignable to other domains)?
I think I'll always use the --all option in case this variant will be
chosen.
Juergen
next prev parent reply other threads:[~2015-10-07 14:47 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 2:11 [PATCH V7 0/7] xen pvusb toolstack work Chunyan Liu
2015-09-25 2:11 ` [PATCH V7 1/7] libxl: export some functions for pvusb use Chunyan Liu
2015-09-25 2:11 ` [PATCH V7 2/7] libxl_read_file_contents: add new entry to read sysfs file Chunyan Liu
2015-09-30 11:22 ` George Dunlap
2015-10-02 13:25 ` Ian Campbell
2015-09-25 2:11 ` [PATCH V7 3/7] libxl: add pvusb API Chunyan Liu
2015-09-30 17:55 ` George Dunlap
2015-10-02 13:31 ` Ian Campbell
2015-10-09 8:12 ` Chun Yan Liu
2015-10-12 7:19 ` Chun Yan Liu
2015-10-12 13:46 ` George Dunlap
2015-10-13 1:46 ` Chun Yan Liu
2015-10-13 13:15 ` George Dunlap
2015-10-13 13:19 ` George Dunlap
2015-10-13 13:30 ` Ian Campbell
2015-10-14 2:29 ` Chun Yan Liu
2015-10-08 14:41 ` Ian Jackson
2015-10-08 14:54 ` Ian Campbell
2015-10-08 15:16 ` Ian Jackson
2015-10-12 7:00 ` Chun Yan Liu
2015-09-25 2:11 ` [PATCH V7 4/7] libxl: add libxl_device_usb_assignable_list API Chunyan Liu
2015-10-01 11:32 ` George Dunlap
2015-09-25 2:11 ` [PATCH V7 5/7] xl: add pvusb commands Chunyan Liu
2015-10-01 17:02 ` George Dunlap
2015-10-02 13:35 ` Ian Campbell
2015-10-02 15:17 ` George Dunlap
2015-10-02 15:29 ` Ian Campbell
2015-10-09 7:15 ` Chun Yan Liu
2015-09-25 2:11 ` [PATCH V7 6/7] xl: add usb-assignable-list command Chunyan Liu
2015-10-06 16:55 ` George Dunlap
2015-10-07 8:40 ` Ian Campbell
2015-10-07 9:55 ` Juergen Gross
2015-10-07 10:08 ` Ian Campbell
2015-10-07 10:10 ` George Dunlap
2015-10-07 10:15 ` George Dunlap
2015-10-07 10:35 ` Christiane Groß
2015-10-07 11:09 ` Ian Campbell
2015-10-07 11:20 ` George Dunlap
2015-10-07 11:25 ` Juergen Gross
2015-10-07 11:32 ` George Dunlap
2015-10-07 11:37 ` Ian Campbell
2015-10-07 11:39 ` Juergen Gross
2015-10-07 11:43 ` Ian Campbell
2015-10-07 11:39 ` Ian Campbell
2015-10-07 11:49 ` Juergen Gross
2015-10-07 11:55 ` Ian Campbell
2015-10-07 12:05 ` Juergen Gross
2015-10-07 12:51 ` Ian Campbell
2015-10-07 13:21 ` George Dunlap
2015-10-07 13:54 ` Juergen Gross
2015-10-07 14:05 ` Ian Campbell
2015-10-07 14:26 ` Juergen Gross
2015-10-07 14:35 ` George Dunlap
2015-10-07 14:47 ` Juergen Gross [this message]
2015-10-07 15:03 ` George Dunlap
2015-10-07 15:13 ` Juergen Gross
2015-10-07 14:10 ` George Dunlap
2015-09-25 2:11 ` [PATCH V7 7/7] domcreate: support pvusb in configuration file Chunyan Liu
2015-10-07 15:06 ` George Dunlap
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=5615308F.3090105@suse.com \
--to=jgross@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=cyliu@suse.com \
--cc=dunlapg@umich.edu \
--cc=george.dunlap@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jfehlig@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.