From: "Alexandre Courbot" <gnurou@gmail.com>
To: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>
Cc: "Albert Esteve" <aesteve@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
gurchetansingh@google.com, daniel.almeida@collabora.com,
adelva@google.com, changyeon@google.com,
nicolas.dufresne@collabora.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, virtualization@lists.linux.dev
Subject: Re: [PATCH v3] media: add virtio-media driver
Date: Wed, 18 Jun 2025 23:16:47 +0900 [thread overview]
Message-ID: <DAPQ1LPH05P4.HLIMQEJCRHLX@gmail.com> (raw)
In-Reply-To: <20250617104938.09d21b7c@foz.lan>
Hi Mauro,
On Tue Jun 17, 2025 at 5:49 PM JST, Mauro Carvalho Chehab wrote:
> Hi Alex,
>
> Em Tue, 27 May 2025 23:03:39 +0900
> Alexandre Courbot <gnurou@gmail.com> escreveu:
>
>> > > > Btw, I was looking at:
>> > > >
>> > > > https://github.com/chromeos/virtio-media
>> > > >
>> > > > (I'm assuming that this is the QEMU counterpart, right?)
>> > >
>> > > crosvm actually, but QEMU support is also being worked on.
>> >
>> > Do you have already QEMU patches? The best is to have the Kernel driver
>> > submitted altogether with QEMU, as Kernel developers need it to do the
>> > tests. In my case, I never use crosvm, and I don't have any Chromebook
>> > anymore.
>>
>> IIRC Albert Esteve was working on this, maybe he can share the current status.
>
> Any news regards to it?
Albert shared the latest status. There is one in-flight patch series
required in qemu [1], and then this branch of vhost-device should
contain the necessary support [2]. Albert is waiting for the virtio spec
to get merged before sending a pull request IIUC.
[1] https://patchew.org/QEMU/20250217164012.246727-1-aesteve@redhat.com/
[2] https://github.com/aesteve-rh/vhost-device/tree/virtio-media
>
>> Note that crosvm does not require a Chromebook, you can build and run
>> it pretty easily on a regular PC. I have put together a document to
>> help with that:
>>
>> https://github.com/chromeos/virtio-media/blob/main/TRY_IT_OUT.md
>
> I started looking on it today. Already installed crossvm (I had to
> install libcap-devel to build it). Still, I'm not familiar with
> crossvm, which is a little be painful. In particular, how can I
> enable network on it and speedup it?
There is a "./tools/examples/setup_network" in the crosvm repository that
will setup a TAP device. Once this is done, you can pass the "--net
tap-name=crosvm_tap" argument to crosvm, and the network device should
be visible and usable.
Let me reply to the rest of your questions in your latest mail, with the
most recent logs.
Cheers,
Alex.
next prev parent reply other threads:[~2025-06-18 14:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 4:08 [PATCH v3] media: add virtio-media driver Alexandre Courbot
2025-04-12 14:27 ` Markus Elfring
2025-05-26 12:13 ` Mauro Carvalho Chehab
2025-05-27 6:14 ` Alexandre Courbot
2025-05-27 9:13 ` Mauro Carvalho Chehab
2025-05-27 13:21 ` Alexandre Courbot
2025-05-27 13:35 ` Mauro Carvalho Chehab
2025-05-27 14:03 ` Alexandre Courbot
2025-05-27 14:42 ` Mauro Carvalho Chehab
2025-06-17 8:49 ` Mauro Carvalho Chehab
2025-06-17 9:03 ` Mauro Carvalho Chehab
2025-06-17 10:20 ` Mauro Carvalho Chehab
2025-06-18 14:27 ` Alexandre Courbot
2025-06-18 15:05 ` Mauro Carvalho Chehab
2025-06-20 12:03 ` Alexandre Courbot
2025-09-08 10:03 ` Mauro Carvalho Chehab
2025-06-18 14:16 ` Alexandre Courbot [this message]
2025-06-18 14:40 ` Mauro Carvalho Chehab
2025-05-27 14:23 ` Michael S. Tsirkin
2025-05-27 14:39 ` Mauro Carvalho Chehab
2025-05-27 15:06 ` Michael S. Tsirkin
2025-05-28 11:07 ` Alexandre Courbot
2025-05-28 16:23 ` Ricardo Ribalda
2025-06-01 9:34 ` Mauro Carvalho Chehab
2025-06-01 10:01 ` Ricardo Ribalda
2025-07-24 17:24 ` Mauro Carvalho Chehab
2025-07-28 11:51 ` Alexandre Courbot
2025-09-09 9:12 ` Mauro Carvalho Chehab
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=DAPQ1LPH05P4.HLIMQEJCRHLX@gmail.com \
--to=gnurou@gmail.com \
--cc=adelva@google.com \
--cc=aesteve@redhat.com \
--cc=changyeon@google.com \
--cc=daniel.almeida@collabora.com \
--cc=eperezma@redhat.com \
--cc=gurchetansingh@google.com \
--cc=hverkuil@xs4all.nl \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=mst@redhat.com \
--cc=nicolas.dufresne@collabora.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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;
as well as URLs for NNTP newsgroup(s).