[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACvf2oUJtxVTuV0qu4z4kV=aSOH5O_8v=UjH_3tr4wCJdXuEjw@mail.gmail.com>
Date: Wed, 23 Aug 2017 17:51:20 +0300
From: Oleksandr Grytsov <al1img@...il.com>
To: Takashi Sakamoto <o-takashi@...amocchi.jp>
Cc: Oleksandr Andrushchenko <andr2000@...il.com>, clemens@...isch.de,
alsa-devel@...a-project.org, xen-devel@...ts.xen.org,
linux-kernel@...r.kernel.org, tiwai@...e.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@...m.com>
Subject: Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized
frontend driver
Hi,
Thank you for detailed explanation.
We understand that emulated interrupt on the frontend side is completely not
acceptable and definitely we need to provide some feedback mechanism from
Dom0 to DomU.
In our case it is technically impossible to provide precise period interrupt
(mostly because our backend is a user space application).
The best we can implement it is provide number of frames (time, bytes etc.)
consumed by real HW. This info will be outdated due to different delays but
we can provide precise timestamps when this info was acquired.
Would this info be useful to update the frontend driver state?
If you have in mind any other solution we would appreciate.
--
Best Regards,
Oleksandr Grytsov.
Powered by blists - more mailing lists