From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Iurii Konovalenko <iurii.konovalenko@globallogic.com>,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
vlad.babchuk@gmail.com,
Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
andrii.anisov@gmail.com, olekstysh@gmail.com, al1img@gmail.com,
Oleksandr Grytsov <oleksandr_grytsov@epam.com>,
xen-devel@lists.xenproject.org, joculator@gmail.com
Subject: Re: [PATCH RESEND v17] xen/sndif: Add sound-device ABI
Date: Thu, 9 Feb 2017 16:17:52 +0200 [thread overview]
Message-ID: <6076a1e5-d508-0b90-ef1c-4a84debdadef@gmail.com> (raw)
In-Reply-To: <38E1E574-0E4D-4495-A509-CB999793E5F5@oracle.com>
On 02/09/2017 02:48 PM, Konrad Rzeszutek Wilk wrote:
> On February 9, 2017 3:46:10 AM EST, Oleksandr Andrushchenko <andr2000@gmail.com> wrote:
>>
>> On 02/08/2017 05:29 PM, Konrad Rzeszutek Wilk wrote:
>>> . snip..
>>>>> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>> Couple of issues I found in sndif while preparing displif for review:
>> 1. missing string constants
>> +#define XENSND_FIELD_BE_VERSIONS "versions"
>> +#define XENSND_FIELD_FE_VERSION "version"
>>
>> 2. I would like to have one more part in the state diagrams section
>> which is currently missing: recovery flow for the case when
>> backend/frontend dies:
>>
>> + *------------------------------- Recovery flow
>> -------------------------------
>> + *
>> + * In case of frontend unrecoverable errors backend handles that as
>> + * if frontend goes into the XenbusStateClosed state.
>> + *
>> + * In case of backend unrecoverable errors frontend tries removing
>> + * the emulated device. If this is possible at the moment of error,
>> + * then frontend goes into the XenbusStateInitialising state and is
>> ready for
>> + * new connection with backend. If the emulated device is still in use
>> and
>> + * cannot be removed, then frontend goes into the
>> XenbusStateReconfiguring state
>> + * until either the emulated device removed or backend initiates a new
>> + * connection. On the emulated device removal frontend goes into the
>> + * XenbusStateInitialising state.
>> + *
>>
> Thanks, feel free to include this and my reviewed by tag.
>
Thank you
>> Thank you,
>> Oleksandr
>
> Thanks!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-02-09 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 8:48 [PATCH RESEND v17] sndif: add ABI for para-virtual sound Oleksandr Andrushchenko
2017-02-08 8:48 ` [PATCH RESEND v17] xen/sndif: Add sound-device ABI Oleksandr Andrushchenko
2017-02-08 15:16 ` Konrad Rzeszutek Wilk
2017-02-08 15:23 ` Oleksandr Andrushchenko
2017-02-08 15:29 ` Konrad Rzeszutek Wilk
2017-02-08 15:30 ` Oleksandr Andrushchenko
2017-02-09 8:46 ` Oleksandr Andrushchenko
2017-02-09 12:48 ` Konrad Rzeszutek Wilk
2017-02-09 14:17 ` Oleksandr Andrushchenko [this message]
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=6076a1e5-d508-0b90-ef1c-4a84debdadef@gmail.com \
--to=andr2000@gmail.com \
--cc=al1img@gmail.com \
--cc=andrii.anisov@gmail.com \
--cc=iurii.konovalenko@globallogic.com \
--cc=joculator@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=oleksandr_grytsov@epam.com \
--cc=olekstysh@gmail.com \
--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).