Re: [Xen-devel] [PATCH v5] sndif: add ABI for Para-virtual sound

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Oleksandr Dmytryshyn writes ("Re: [PATCH v5] sndif: add ABI for Para-virtual 
sound"):
> On Thu, Jan 22, 2015 at 5:41 PM, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> 
> wrote:
> > So for example, much real hardware will have a headphone output and
> > also built-in speakers, and a mic input and built-in microphone.
> 
> > How is this to be exposed to the guest ?
> 
> Every stream handled in the own thread in the frontend driver.
> Frontend sends command (read or write, etc) to the backend and
> this is blocking command (within current stream). So I just
> use different streams for playback and capture.

Right, I gathered that.

> In case if we have
> headphone output and also built-in speakers, and a mic input and
> built-in microphone we will use one stream for the headphone output,
> one stream for the built-in speakers and one stream for the mic input.
> And in this time all devices will be able to work simultaneously.

Perhaps I'm missing something but I don't see where the necessary
information is passed in your protocol specification.

Let us consider only output for now.  How does the guest choose which
of the possibly-several output devices their stream goes to ?  Are
these the multiple stream_id's ?  Are they identified solely by
number ?  Is there a conventional mapping for these streams ?

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel