From: George Dunlap <george.dunlap@citrix.com>
To: Chun Yan Liu <cyliu@suse.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xen.org
Cc: Juergen Gross <JGross@suse.com>,
wei.liu2@citrix.com, ian.campbell@citrix.com,
Ian.Jackson@eu.citrix.com, Jim Fehlig <JFEHLIG@suse.com>,
Simon Cao <caobosimon@gmail.com>
Subject: Re: [PATCH V5 3/7] libxl: add pvusb API
Date: Mon, 10 Aug 2015 11:08:33 +0100 [thread overview]
Message-ID: <55C87821.10504@citrix.com> (raw)
In-Reply-To: <55C488EA020000660005630B@relay2.provo.novell.com>
On 08/07/2015 03:31 AM, Chun Yan Liu wrote:
>>>>>> + ("devid", libxl_devid),
>>>>>> + ("version", integer),
>>>>>> + ("ports", integer),
>>>>>> + ("backend_domid", libxl_domid),
>>>>>> + ("backend_domname", string),
>>>>>> + ])
>>>>>> +
>>>>>> +libxl_device_usb = Struct("device_usb", [
>>>>>> + ("ctrl", libxl_devid),
>>>>>> + ("port", integer),
>>>>>> + ("hostbus", integer),
>>>>>> + ("hostaddr", integer),
>>>>>> + ])
>>
>> I think we do want to plan for the future here by doing something like this:
>>
>> libxl_device_usb = Struct("device_usb", [
>> ("ctrl", libxl_devid),
>> ("port", integer),
>> ("u", KeyedUnion(None, libxl_device_usb_type, "devtype",
>> [("hostdev", Struct(None, [
>> ("hostbus", integer),
>> ("hostaddr", integer) ]))
>> ]))
>> ])
>>
>
> Yes, that's the future look. For pvusb, currenlty with kernel pvusb driver, the
> devtype is not really necessary. But I can add 'devtype' if it is preferred now.
Yes, I think as much as possible we want the interface which is actually
checked in to be forward-compatible.
Thanks!
-George
next prev parent reply other threads:[~2015-08-10 10:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 10:07 [PATCH V5 0/7] xen pvusb toolstack work Chunyan Liu
2015-06-25 10:07 ` [PATCH V5 1/7] libxl: export some functions for pvusb use Chunyan Liu
2015-06-25 10:07 ` [PATCH V5 2/7] libxl_read_file_contents: add new entry to read sysfs file Chunyan Liu
2015-06-25 11:09 ` Ian Jackson
2015-06-26 5:47 ` Chun Yan Liu
2015-06-26 5:48 ` Chun Yan Liu
2015-06-26 13:05 ` Ian Jackson
2015-06-29 10:15 ` Chun Yan Liu
2015-06-29 10:52 ` Ian Jackson
2015-06-30 1:43 ` Chun Yan Liu
2015-06-30 9:08 ` Ian Jackson
2015-06-30 9:32 ` Chun Yan Liu
2015-06-30 9:42 ` Ian Jackson
2015-06-25 10:07 ` [PATCH V5 3/7] libxl: add pvusb API Chunyan Liu
2015-06-25 11:15 ` Ian Jackson
2015-07-07 1:25 ` Chun Yan Liu
2015-07-07 9:57 ` George Dunlap
2015-08-06 3:11 ` Chun Yan Liu
2015-08-06 17:21 ` George Dunlap
2015-08-07 2:31 ` Chun Yan Liu
2015-08-10 10:08 ` George Dunlap [this message]
2015-08-07 7:41 ` Chun Yan Liu
2015-07-16 15:01 ` Juergen Gross
2015-06-25 10:07 ` [PATCH V5 4/7] libxl: add libxl_device_usb_assignable_list API Chunyan Liu
2015-06-25 10:07 ` [PATCH V5 5/7] xl: add pvusb commands Chunyan Liu
2015-06-25 10:07 ` [PATCH V5 6/7] xl: add usb-assignable-list command Chunyan Liu
2015-06-25 10:07 ` [PATCH V5 7/7] domcreate: support pvusb in configuration file Chunyan Liu
2015-07-13 10:08 ` Juergen Gross
2015-08-06 2:49 ` Chun Yan Liu
2015-07-13 10:09 ` [PATCH V5 0/7] xen pvusb toolstack work Juergen Gross
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=55C87821.10504@citrix.com \
--to=george.dunlap@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JFEHLIG@suse.com \
--cc=JGross@suse.com \
--cc=caobosimon@gmail.com \
--cc=cyliu@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.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.