> Feature bits
>
>
> VIRTIO_SND_F_PCM_OUTPUT
> VIRTIO_SND_F_PCM_INPUT
>
> and new ones would be
>
> VIRTIO_SND_F_PCM_EVT_PERIOD - support elapsed period notifications
> VIRTIO_SND_F_PCM_EVT_XRUN - support underrun/overrun notifications
> VIRTIO_SND_F_PCM_MSG - support message-based
Again, thank you all for your valuable comments! There were quite a lot of
suggestions, so I briefly gathered all of them.
Feature bits
VIRTIO_SND_F_PCM_OUTPUT
VIRTIO_SND_F_PCM_INPUT
and new ones would be
VIRTIO_SND_F_PCM_EVT_PERIOD - support elapsed period notifications
VIRTIO_S
Hi Gerd,
On Mittwoch, 20. November 2019 12:29:29 CET Gerd Hoffmann wrote:
> Hi,
>
> > > > > 3. No support for getting plane requirements from the device (sg vs
> > > > > contig,
> > > > > size, stride alignment, plane count).
> > > >
> > > > There is actually a bigger difference that results i
Hi,
> > In general if I have guest core affinity then hypervisor context
> > switching for that guest is in low 10s of uS (depends on hypervisor
> > of course and HW). This is good enough for low latency audio.
> That's why we are really curious how other people target such issues
> with audio
On Wed, 20 Nov 2019 18:44:51 +0100
Jean-Philippe Brucker wrote:
> On Wed, Nov 20, 2019 at 06:27:34PM +0100, Cornelia Huck wrote:
> > > +\begin{lstlisting}
> > > +struct virtio_iommu_config {
> > > + le64 page_size_mask;
> > > + struct virtio_iommu_range_64 {
> > > +le64 start;
> > > +le
