From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: lars.kurth@citrix.com, iurii.konovalenko@globallogic.com,
vlad.babchuk@gmail.com, ian.jackson@eu.citrix.com,
oleksandr.dmytryshyn@globallogic.com, tim@xen.org,
julien.grall@arm.com, andrii.anisov@gmail.com,
olekstysh@gmail.com, embedded-pv-devel@lists.xenproject.org,
al1img@gmail.com, david.vrabel@citrix.com, JBeulich@suse.com,
xen-devel@lists.xenproject.org, joculator@gmail.com
Subject: Re: [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.
Date: Thu, 26 Jan 2017 13:23:54 +0200 [thread overview]
Message-ID: <c81fb1eb-6de7-51c2-e868-c99b4f50d0b1@gmail.com> (raw)
In-Reply-To: <1485428970.32103.143.camel@citrix.com>
On 01/26/2017 01:09 PM, Dario Faggioli wrote:
> On Thu, 2017-01-26 at 12:02 +0200, Oleksandr Andrushchenko wrote:
>> Hi, Konrad!
>>
>> First of all thank you very much for the valuable comments
>>
>> and your time!
>>
>> The number of changes (mostly in description) is going to
>>
>> be huge, so do you think I can publish something like
>>
>> "RFC v16" so we can discuss the updated patch?
>>
> Konrad's call, but why you want to introduce the 'RFC' tag now? I'd
> just go with v16...
no particular reason, will use v16 )
>
>> On 01/24/2017 09:13 PM, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Dec 05, 2016 at 03:05:29PM +0200, Oleksandr Andrushchenko
>>> wrote:
>>>>
>>>> + * Example for the frontend running in domain 5, instance of the
>>>> driver
>>>> + * in the front is 0 (single or first PV driver), device id 2,
>>>> + * first stream (0):
>>>> + * /local/domain/<frontend_id>/device/vsnd/<drv_idx>/
>>>> + * device/<dev_id>/stream/<stream_idx>/type = "p"
>>>> + * /local/domain/5/device/vsnd/0/device/2/stream/0/type = "p"
>>> Why do you need 'device' ?
>> just for clarity: the hierarchy of the sound driver would
>> be that a device may have multiple different streams.
>> So, from readability POV I would still have "device" in place
>> From xenstore documentation: "Data should generally be
>> human-readable for ease of management and debugging "
>> I assume this also applies to the structure as well
>>
> Perhaps:
>
> /local/domain/<frontend_id>/device/vsnd/<drv_idx>/dev-<dev_id>/stream-<stream_idx>/...
>
>>> Could not this be:
>>>
>>> /local/domain/5/device/vsnd/0/2/stream/0/type = "p" ?
>> then one has to know that "2" stands for device.
>> see above, I would keep "device" here
> /local/domain/5/device/vsnd/0/dev-2/stream-0/type = "p"
>
> Or, with no '-':
>
> /local/domain/5/device/vsnd/0/dev2/stream0/type = "p"
>
> Just my 2 cents...
1. Well, the only reason I have "device" here is for clarity
and consistency: sound card owns PCM devices, PCM device owns
streams
We could probably have "pcm-dev" instead of "device" here,
so we do not collide with xen device.
2. "dev-%d" or "dev%d", "stream-%d" or "stream%d"
IMO, we already have indices employed in xenstore,
e.g. "domain/5", not "domain-5" or "domain5"
So, is the PCM device in question any different from domain
from this POV? To me - not, so this is why I use "device/%d"
> Dario
Thank you,
Oleksandr
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-26 11:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 13:05 [PATCH v15] sndif: add ABI for para-virtual sound Oleksandr Andrushchenko
2016-12-05 13:05 ` [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other Oleksandr Andrushchenko
2016-12-08 15:13 ` Oleksandr Andrushchenko
2016-12-22 7:21 ` Oleksandr Andrushchenko
2016-12-22 13:00 ` Konrad Rzeszutek Wilk
2017-01-24 19:13 ` Konrad Rzeszutek Wilk
2017-01-26 10:02 ` Oleksandr Andrushchenko
2017-01-26 11:09 ` Dario Faggioli
2017-01-26 11:23 ` Oleksandr Andrushchenko [this message]
2017-01-26 11:54 ` Dario Faggioli
2017-01-26 12:22 ` Oleksandr Andrushchenko
2017-01-27 14:52 ` Konrad Rzeszutek Wilk
2017-01-27 15:14 ` Konrad Rzeszutek Wilk
2017-01-27 15:50 ` Oleksandr Andrushchenko
2017-01-27 16:36 ` Konrad Rzeszutek Wilk
2017-01-27 17:13 ` Oleksandr Andrushchenko
2017-01-27 18:13 ` Konrad Rzeszutek Wilk
2017-01-27 18:38 ` Oleksandr Andrushchenko
2017-01-27 18:57 ` Konrad Rzeszutek Wilk
2017-01-30 6:49 ` Oleksandr Andrushchenko
2017-02-07 19:16 ` Konrad Rzeszutek Wilk
2017-02-07 19:22 ` Oleksandr Andrushchenko
2017-01-11 8:00 ` [PATCH v15] sndif: add ABI for para-virtual sound Oleksandr Andrushchenko
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=c81fb1eb-6de7-51c2-e868-c99b4f50d0b1@gmail.com \
--to=andr2000@gmail.com \
--cc=JBeulich@suse.com \
--cc=al1img@gmail.com \
--cc=andrii.anisov@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=embedded-pv-devel@lists.xenproject.org \
--cc=ian.jackson@eu.citrix.com \
--cc=iurii.konovalenko@globallogic.com \
--cc=joculator@gmail.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=olekstysh@gmail.com \
--cc=tim@xen.org \
--cc=vlad.babchuk@gmail.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).