[alsa-devel] paravirtualized alsa kernel driver for XEN

Clemens Ladisch clemens at ladisch.de
Wed Mar 21 14:37:56 CET 2012

Stefano Panella wrote:
> On 20/03/12 13:10, Clemens Ladisch wrote:
> > The delay between the DMA and the DAC output would be reported by
> > adjusting runtime->delay, but drivers usually do not bother to do this,
> > except when this delay becomes rather large because of additional
> > queueing, e.g., in the USB driver.
> ok, I was wondering about applications like skype, trying to do some
> background noise cancellation, or to eliminate echo when using speakers.
> I was thinking in this case the delay should be accurate for Playback
> and Capture as well, or am I wrong?

If the sound data is regularly moved from the VM's buffer to the host's
buffer, then the additional latency of the host is big enough that it's
worth reporting.

If you map the host's buffer into the VM's address space, there is no
additional latency, but I don't know if this is feasible.  If not, you
could also use the pcm_ops.copy callback to copy the data from the VM
to the host as soon as the application writes it.

> Who is currently the linux kernel alsa driver mantainer?

See "SOUND" in the MAINTAINERS file.


More information about the Alsa-devel mailing list