From: "Michael S. Tsirkin" <mst@redhat.com>
To: Roman Kiryanov <rkir@google.com>
Cc: virtio-dev@lists.oasis-open.org
Subject: Re: [virtio-dev] virtio-snd spec question
Date: Wed, 2 Feb 2022 02:44:22 -0500 [thread overview]
Message-ID: <20220202024251-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAOGAQerz6dM+ZStRUiFaSmYCQJsbpij5=S+OU=Ck+bbUKOR+Pw@mail.gmail.com>
On Tue, Feb 01, 2022 at 03:57:10PM -0800, Roman Kiryanov wrote:
> Hello,
>
> I work in Android Studio Emulator and I am currently implementing a virtio-snd
> device. We found a spec draft here:
>
> https://github.com/oasis-tcs/virtio-spec/commit/
> e73c8cdf3e822fd83c26c6de964a947670f93cc3#
> diff-73045e70aeaf45f93087610437b705e2d320c82a9d29b4027721f5f5f3918dc5
>
> It mentions four virtqueues: ctl, event, rx and tx. It is not very clear where
> a virtio-snd device should put responses to the ctl requests from the linux
> kernel driver. There is a kernel driver implementation and we have a
> virtio-snd device implemented in another emulator, it uses the same virtqueue
> (ctl) to put ctl responses and the current kernel driver seems happy with this.
>
> Do you know if this is expected behavior? I am far from an expert here, but I
> believe the device and the kernel will race here by reading from the same
> virtqueue: the device could read VirtQueueElement produced by itself before the
> kernel if the kernel is not fast enough.
>
> Thank you.
>
> Regards,
> Roman.
Could you explain a bit more? which function in the kernel driver are
you referring to?
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2022-02-02 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 23:57 [virtio-dev] virtio-snd spec question Roman Kiryanov
2022-02-02 7:44 ` Michael S. Tsirkin [this message]
2022-02-02 18:43 ` Roman Kiryanov
2022-02-02 22:01 ` Michael S. Tsirkin
2022-02-03 10:36 ` Stefan Hajnoczi
[not found] ` <CAAQ-SiNEk3OzBK6DGtufWKS+wqysZeN2Ntp3tHa_3N=dbFCrSg@mail.gmail.com>
2022-02-11 5:41 ` Roman Kiryanov
2022-02-06 15:23 ` Anton Yakovlev
2022-02-18 6:31 ` Roman Kiryanov
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=20220202024251-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=rkir@google.com \
--cc=virtio-dev@lists.oasis-open.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.