From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Oleksandr Grytsov <al1img@gmail.com>,
clemens@ladisch.de
Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>,
alsa-devel@alsa-project.org, tiwai@suse.com,
linux-kernel@vger.kernel.org, xen-devel@lists.xen.org
Subject: Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver
Date: Fri, 18 Aug 2017 10:23:05 +0300 [thread overview]
Message-ID: <b129960e-b38f-ea94-3e4a-3cd409f7a707@gmail.com> (raw)
In-Reply-To: <ad4f2201-bfab-415d-0120-308989653628@sakamocchi.jp>
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 use-case is the most tough thing in
>> equation)
>
> 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 para-virtual backend in Dom0 and serves all the
frontends running in DomU(s).
Other ALSA/PulseAudio clients in Dom0 are also allowed to run at the
same time.
>
> Regards
>
> Takashi Sakamoto
Thank you,
Oleksandr
[1] https://github.com/xen-troops/snd_be
next prev parent reply other threads:[~2017-08-18 7:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 12:22 [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 01/12] ALSA: vsnd: Introduce Xen para-virtualized sound " Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 02/12] ALSA: vsnd: Implement driver's probe/remove Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 03/12] ALSA: vsnd: Implement Xen bus state handling Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 04/12] ALSA: vsnd: Read sound driver configuration from Xen store Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 05/12] ALSA: vsnd: Implement Xen event channel handling Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 06/12] ALSA: vsnd: Implement handling of shared buffers Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 07/12] ALSA: vsnd: Introduce ALSA virtual sound driver Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 08/12] ALSA: vsnd: Initialize virtul sound card Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 09/12] ALSA: vsnd: Add timer for period interrupt emulation Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 10/12] ALSA: vsnd: Implement ALSA PCM operations Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 11/12] ALSA: vsnd: Implement communication with backend Oleksandr Andrushchenko
2017-08-07 12:22 ` [PATCH RESEND1 12/12] ALSA: vsnd: Introduce Kconfig option to enable Xen PV sound Oleksandr Andrushchenko
2017-08-10 3:14 ` [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver Takashi Sakamoto
2017-08-10 8:10 ` Oleksandr Andrushchenko
2017-08-17 10:05 ` Oleksandr Grytsov
2017-08-18 5:43 ` Takashi Sakamoto
2017-08-18 5:56 ` Oleksandr Andrushchenko
2017-08-18 7:17 ` Takashi Sakamoto
2017-08-18 7:23 ` Oleksandr Andrushchenko [this message]
2017-08-22 2:43 ` Takashi Sakamoto
2017-08-23 14:51 ` Oleksandr Grytsov
2017-08-24 4:38 ` Takashi Sakamoto
2017-08-24 7:04 ` Oleksandr Andrushchenko
2017-09-04 7:21 ` Oleksandr Andrushchenko
2017-09-05 7:24 ` [alsa-devel] " Clemens Ladisch
2017-09-12 7:52 ` Oleksandr Grytsov
2017-09-19 8:57 ` Oleksandr Andrushchenko
2017-09-26 11:35 ` Oleksandr Andrushchenko
2017-10-04 6:50 ` Oleksandr Andrushchenko
2017-10-13 6:15 ` Oleksandr Andrushchenko
2017-10-30 6:33 ` [RFC] " Oleksandr Andrushchenko
2017-11-02 9:44 ` Takashi Sakamoto
2017-11-02 9:55 ` 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=b129960e-b38f-ea94-3e4a-3cd409f7a707@gmail.com \
--to=andr2000@gmail.com \
--cc=al1img@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=oleksandr_andrushchenko@epam.com \
--cc=tiwai@suse.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 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).