Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

ping On 10/04/2017 09:50 AM, Oleksandr Andrushchenko wrote: gentle reminder On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote: Clemens, Sakamoto-san, could you please review the below if you by chance have a minute? Thank you, Oleksandr On 09/19/2017 11:57 AM, Oleksandr Andrushchenko

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

ping On 10/04/2017 09:50 AM, Oleksandr Andrushchenko wrote: gentle reminder On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote: Clemens, Sakamoto-san, could you please review the below if you by chance have a minute? Thank you, Oleksandr On 09/19/2017 11:57 AM, Oleksandr Andrushchenko

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

gentle reminder On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote: Clemens, Sakamoto-san, could you please review the below if you by chance have a minute? Thank you, Oleksandr On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wrote: Hi, all! We did some work on implementing the idea

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

gentle reminder On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote: Clemens, Sakamoto-san, could you please review the below if you by chance have a minute? Thank you, Oleksandr On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wrote: Hi, all! We did some work on implementing the idea

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Clemens, Sakamoto-san, could you please review the below if you by chance have a minute? Thank you, Oleksandr On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wrote: Hi, all! We did some work on implementing the idea with feedback events from the backend to the frontend. Please see attached

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Clemens, Sakamoto-san, could you please review the below if you by chance have a minute? Thank you, Oleksandr On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wrote: Hi, all! We did some work on implementing the idea with feedback events from the backend to the frontend. Please see attached

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, all! We did some work on implementing the idea with feedback events from the backend to the frontend. Please see attached the changes to the existing sndif protocol [1]: 1. Introduced a new event channel from back to front 2. New event with number of bytes played/captured

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, all! We did some work on implementing the idea with feedback events from the backend to the frontend. Please see attached the changes to the existing sndif protocol [1]: 1. Introduced a new event channel from back to front 2. New event with number of bytes played/captured

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Tue, Sep 5, 2017 at 10:24 AM, Clemens Ladisch wrote: > Oleksandr Andrushchenko wrote: We understand that emulated interrupt on the frontend side is completely not acceptable > > Allow me to expand on that: Proper synchronization requires that the > exact

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Tue, Sep 5, 2017 at 10:24 AM, Clemens Ladisch wrote: > Oleksandr Andrushchenko wrote: We understand that emulated interrupt on the frontend side is completely not acceptable > > Allow me to expand on that: Proper synchronization requires that the > exact position is

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Oleksandr Andrushchenko wrote: >>> We understand that emulated interrupt on the frontend side is completely not >>> acceptable Allow me to expand on that: Proper synchronization requires that the exact position is communicated, not estimated. Just because the nominal rate of the stream is known

Re: [alsa-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Oleksandr Andrushchenko wrote: >>> We understand that emulated interrupt on the frontend side is completely not >>> acceptable Allow me to expand on that: Proper synchronization requires that the exact position is communicated, not estimated. Just because the nominal rate of the stream is known

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On 08/24/2017 10:04 AM, Oleksandr Andrushchenko wrote: Hello, On 08/24/2017 07:38 AM, Takashi Sakamoto wrote: On Aug 23 2017 23:51, Oleksandr Grytsov wrote: Hi, Thank you for detailed explanation. We understand that emulated interrupt on the frontend side is completely not acceptable and

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On 08/24/2017 10:04 AM, Oleksandr Andrushchenko wrote: Hello, On 08/24/2017 07:38 AM, Takashi Sakamoto wrote: On Aug 23 2017 23:51, Oleksandr Grytsov wrote: Hi, Thank you for detailed explanation. We understand that emulated interrupt on the frontend side is completely not acceptable and

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hello, On 08/24/2017 07:38 AM, Takashi Sakamoto wrote: On Aug 23 2017 23:51, Oleksandr Grytsov wrote: 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

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hello, On 08/24/2017 07:38 AM, Takashi Sakamoto wrote: On Aug 23 2017 23:51, Oleksandr Grytsov wrote: 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

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Aug 23 2017 23:51, Oleksandr Grytsov wrote: 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

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Aug 23 2017 23:51, Oleksandr Grytsov wrote: 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

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

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

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, On Aug 18 2017 16:23, Oleksandr Andrushchenko wrote: >> You mean that any alsa-lib or libpulse applications run on Dom0 as a >> backend driver for the frontend driver on DomU? >> > No, the sound backend [1] is a user-space application (ALSA/PulseAudio > client) > which runs as a Xen

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, On Aug 18 2017 16:23, Oleksandr Andrushchenko wrote: >> You mean that any alsa-lib or libpulse applications run on Dom0 as a >> backend driver for the frontend driver on DomU? >> > No, the sound backend [1] is a user-space application (ALSA/PulseAudio > client) > which runs as a Xen

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On 08/18/2017 10:17 AM, Takashi Sakamoto wrote: On Aug 18 2017 14:56, Oleksandr Andrushchenko wrote: Taking into account the fact that the backend we have is a user-space application running on top of ALSA/PulseAudio we cannot get HW pointers from actual hardware by any means (PulseAudio

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On 08/18/2017 10:17 AM, Takashi Sakamoto wrote: On Aug 18 2017 14:56, Oleksandr Andrushchenko wrote: Taking into account the fact that the backend we have is a user-space application running on top of ALSA/PulseAudio we cannot get HW pointers from actual hardware by any means (PulseAudio

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Aug 18 2017 14:56, Oleksandr Andrushchenko wrote: Taking into account the fact that the backend we have is a user-space application running on top of ALSA/PulseAudio we cannot get HW pointers from actual hardware by any means (PulseAudio use-case is the most tough thing in equation) You

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Aug 18 2017 14:56, Oleksandr Andrushchenko wrote: Taking into account the fact that the backend we have is a user-space application running on top of ALSA/PulseAudio we cannot get HW pointers from actual hardware by any means (PulseAudio use-case is the most tough thing in equation) You

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hello, On 08/18/2017 08:43 AM, Takashi Sakamoto wrote: On Aug 17 2017 19:05, Oleksandr Grytsov wrote: So, from the above we think that period elapsed event derived in the described ways may not improve latency and will complicate the system. So, for that reason we are thinking of the option

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hello, On 08/18/2017 08:43 AM, Takashi Sakamoto wrote: On Aug 17 2017 19:05, Oleksandr Grytsov wrote: So, from the above we think that period elapsed event derived in the described ways may not improve latency and will complicate the system. So, for that reason we are thinking of the option

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Aug 17 2017 19:05, Oleksandr Grytsov wrote: So, from the above we think that period elapsed event derived in the described ways may not improve latency and will complicate the system. So, for that reason we are thinking of the option 2) (Positions of actual data transmission in any serial

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Aug 17 2017 19:05, Oleksandr Grytsov wrote: So, from the above we think that period elapsed event derived in the described ways may not improve latency and will complicate the system. So, for that reason we are thinking of the option 2) (Positions of actual data transmission in any serial

Re: [Xen-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Thu, Aug 10, 2017 at 11:10 AM, Oleksandr Andrushchenko wrote: > Hi, > > thank you very much for valuable comments and your time! > > > On 08/10/2017 06:14 AM, Takashi Sakamoto wrote: >> >> Hi, >> >> On Aug 7 2017 21:22, Oleksandr Andrushchenko wrote: >>> >>> From: Oleksandr

Re: [Xen-devel] [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

On Thu, Aug 10, 2017 at 11:10 AM, Oleksandr Andrushchenko wrote: > Hi, > > thank you very much for valuable comments and your time! > > > On 08/10/2017 06:14 AM, Takashi Sakamoto wrote: >> >> Hi, >> >> On Aug 7 2017 21:22, Oleksandr Andrushchenko wrote: >>> >>> From: Oleksandr Andrushchenko >>>

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, thank you very much for valuable comments and your time! On 08/10/2017 06:14 AM, Takashi Sakamoto wrote: Hi, On Aug 7 2017 21:22, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko This patch series adds support for Xen [1] para-virtualized

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, thank you very much for valuable comments and your time! On 08/10/2017 06:14 AM, Takashi Sakamoto wrote: Hi, On Aug 7 2017 21:22, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko This patch series adds support for Xen [1] para-virtualized sound frontend driver. It

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, On Aug 7 2017 21:22, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko This patch series adds support for Xen [1] para-virtualized sound frontend driver. It implements the protocol from include/xen/interface/io/sndif.h with the following

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, On Aug 7 2017 21:22, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko This patch series adds support for Xen [1] para-virtualized sound frontend driver. It implements the protocol from include/xen/interface/io/sndif.h with the following limitations: - mute/unmute is not

[PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

From: Oleksandr Andrushchenko This patch series adds support for Xen [1] para-virtualized sound frontend driver. It implements the protocol from include/xen/interface/io/sndif.h with the following limitations: - mute/unmute is not supported - get/set volume is

[PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

From: Oleksandr Andrushchenko This patch series adds support for Xen [1] para-virtualized sound frontend driver. It implements the protocol from include/xen/interface/io/sndif.h with the following limitations: - mute/unmute is not supported - get/set volume is not supported Volume control is not