[pulseaudio-discuss] PulseAudio Xen module
gboutsioukis at gmail.com
Mon Oct 31 09:33:18 PDT 2011
Hello PulseAudio people!
As part of a Google Summer of code project for Xen during this summer, I
wrote a PulseAudio module that acts as the frontend part of a Xen
paravirtualized audio driver. Basically what it does is push audio frames
over a ring buffer placed in memory shared between different Xen domains,
using Xen's interrupt-like events to notify the playback backend that audio
data is available.
The driver right now works well and we are thinking of the best possible
way to distribute it. Since (and correct me if I'm wrong) it's not possible
to build PulseAudio modules with the usual headers provided for PulseAudio
applications, we can't simply merge it with Xen's build system without the
whole. We'd like to be able to build something like a
pulseaudio-modules-xen package for a few common distro's, but in the most
(reasonably) maintenance-free way possible.
So, what would it take to check this into PulseAudio? (and build only when
the Xen headers are found)
You can find the code here:
(ignore the xenpv-source module, doesn't really work yet)
The playback module was based on pipe-sink. There are definitely some
mistakes in there (I'm not even close to a sound programming expert), but
if it's an issue of code quality I could clean it up to an acceptable state.
There's a design document that describes the driver's design in detail here:
For more info on how paravirtualized drivers in general work in Xen see:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pulseaudio-discuss