From: Takashi Iwai <tiwai@suse.de>
To: "Ughreja, Rakesh A" <rakesh.a.ughreja@intel.com>
Cc: "'alsa-devel@alsa-project.org'" <alsa-devel@alsa-project.org>
Subject: Re: Para-virtualized audio drivers
Date: Thu, 20 Oct 2016 17:26:01 +0200 [thread overview]
Message-ID: <s5hpomvghyu.wl-tiwai@suse.de> (raw)
In-Reply-To: <85DFEED57DC57344B2483EF7BF8CB60552C5B457@BGSMSX104.gar.corp.intel.com>
On Mon, 17 Oct 2016 05:01:47 +0200,
Ughreja, Rakesh A wrote:
>
> Hi Takashi and all,
>
> I have some need to develop para virtualized audio drivers which can
> work with XEN hypervisor.
>
> I see some attempt was made in the past.
> https://lists.xen.org/archives/html/xen-devel/2015-01/msg02125.html
>
> I see one more material but with no code.
> http://rd.springer.com/chapter/10.1007%2F978-94-007-2105-0_46
>
> I am thinking to develop pv-audio-frontend (running on Dom1) and
> pv-audio-backend (running on Dom0) drivers all at kernel level.
> Backend driver owns the hardware. Frontend driver communicates with
> backend driver using XENbus framework just like storage and network PV
> drivers.
>
> Before I start, I wanted to check if there is any other
> work that has been done which I can take as base ?
I don't know of any other existing implementation for Xen. The
question would be rather how you would implement the backend.
Is it about Intel hardware as Liam has been working on? Or is it
targeted as a generic Xen stuff like the patches you mentioned in the
above? The patchset above was about the user-space backend, IIRC.
Takashi
next prev parent reply other threads:[~2016-10-20 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 3:01 Para-virtualized audio drivers Ughreja, Rakesh A
2016-10-19 10:27 ` Liam Girdwood
2016-10-20 15:26 ` Takashi Iwai [this message]
2016-10-20 17:02 ` Ughreja, Rakesh A
2016-10-20 18:09 ` Takashi Iwai
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=s5hpomvghyu.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=rakesh.a.ughreja@intel.com \
/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