From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Gordeev <quic_agordeev@quicinc.com>
Cc: virtio-comment@lists.linux.dev,
Trilok Soni <quic_tsoni@quicinc.com>,
Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>
Subject: Re: virtio-video device IDs
Date: Mon, 23 Dec 2024 05:57:01 -0500 [thread overview]
Message-ID: <20241223055543-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <bbef01ea-2085-49a8-bc6a-76cf66a6183d@quicinc.com>
On Fri, Dec 20, 2024 at 05:47:11PM +0100, Alexander Gordeev wrote:
> Hi,
>
> Currently there are two device IDs assigned for the future virtio video device:
> * 30 for the encoder
> * 31 for the decoder
> I received feedback from our internal reviewers that in some cases it would be better to use as few virtqueues as possible. So if a single piece of HW supports both encoder and decoder functions, then it is better to have a single virtual device, that provides both functions as well. The specific function can be selected per stream then.
> Is it OK to make changes to the reserved IDs?
> Are there any other concerns?
>
> Thanks
Basically, we need to make sure there are no conflicts.
The IDs were reserved by google and chromium guys.
If you want to make changes, get in touch with them
and get their ACK please.
But generally, it's easier to just reserve another ID
for an encoder/decoder device.
We are not short on these.
--
MST
next prev parent reply other threads:[~2024-12-23 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 16:47 virtio-video device IDs Alexander Gordeev
2024-12-22 14:14 ` Parav Pandit
2024-12-27 11:15 ` Alexander Gordeev
2024-12-23 10:57 ` Michael S. Tsirkin [this message]
2024-12-27 11:14 ` Alexander Gordeev
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=20241223055543-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=quic_agordeev@quicinc.com \
--cc=quic_svaddagi@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=virtio-comment@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox