From: Dmitry Sepp <dmitry.sepp@opensynergy.com>
To: Saket Sinha <saket.sinha89@gmail.com>
Cc: Samiullah Khawaja <samiullah.khawaja@opensynergy.com>,
virtio-dev@lists.oasis-open.org, Alex Lau <alexlau@chromium.org>,
Kiran Pawar <Kiran.Pawar@opensynergy.com>,
Alexandre Courbot <acourbot@chromium.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Tomasz Figa <tfiga@chromium.org>,
Keiichi Watanabe <keiichiw@chromium.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Pawel Osciak <posciak@chromium.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [virtio-dev] Re: Fwd: Qemu Support for Virtio Video V4L2 driver
Date: Mon, 11 May 2020 13:25:23 +0200 [thread overview]
Message-ID: <2515515.r9knKAEANn@os-lin-dmo> (raw)
In-Reply-To: <CAK25hWM-hLdk=MSKgceumOUo9ZNBrrmM8qSe7MvTUAPGmur_HQ@mail.gmail.com>
Hi Saket,
On Montag, 11. Mai 2020 13:05:53 CEST Saket Sinha wrote:
> Hi Keiichi,
>
> I do not support the approach of QEMU implementation forwarding
> requests to the host's vicodec module since this can limit the scope
> of the virtio-video device only for testing,
That was my understanding as well.
> which instead can be used with multiple use cases such as -
>
> 1. VM gets access to paravirtualized camera devices which shares the
> video frames input through actual HW camera attached to Host.
This use-case is out of the scope of virtio-video. Initially I had a plan to
support capture-only streams like camera as well, but later the decision was
made upstream that camera should be implemented as separate device type. We
still plan to implement a simple frame capture capability as a downstream
patch though.
>
> 2. If Host has multiple video devices (especially in ARM SOCs over
> MIPI interfaces or USB), different VM can be started or hotplugged
> with selective video streams from actual HW video devices.
We do support this in our device implementation. But spec in general has no
requirements or instructions regarding this. And it is in fact flexible enough
to provide abstraction on top of several HW devices.
>
> Also instead of using libraries like Gstreamer in Host userspace, they
> can also be used inside the VM userspace after getting access to
> paravirtualized HW camera devices .
>
Regarding the cameras, unfortunately same as above.
Best regards,
Dmitry.
> Regards,
> Saket Sinha
>
> On Mon, May 11, 2020 at 12:20 PM Keiichi Watanabe <keiichiw@chromium.org>
wrote:
> > Hi Dmitry,
> >
> > On Mon, May 11, 2020 at 6:40 PM Dmitry Sepp <dmitry.sepp@opensynergy.com>
wrote:
> > > Hi Saket and all,
> > >
> > > As we are working with automotive platforms, unfortunately we don't plan
> > > any Qemu reference implementation so far.
> > >
> > > Of course we are ready to support the community if any help is needed.
> > > Is
> > > there interest in support for the FWHT format only for testing purpose
> > > or you want a full-featured implementation on the QEMU side?
> >
> > I guess we don't need to implement the codec algorithm in QEMU.
> > Rather, QEMU forwards virtio-video requests to the host video device
> > or a software library such as GStreamer or ffmpeg.
> > So, what we need to implement in QEMU is a kind of API translation,
> > which shouldn't care about actual video formats so much.
> >
> > Regarding the FWHT format discussed in the patch thread [1], in my
> > understanding, Hans suggested to have QEMU implementation forwarding
> > requests to the host's vicodec module [2].
> > Then, we'll be able to test the virtio-video driver on QEMU on Linux
> > even if the host Linux has no hardware video decoder.
> > (Please correct me if I'm wrong.)
> >
> > Let me add Hans and Linux media ML in CC.
> >
> > [1] https://patchwork.linuxtv.org/patch/61717/
> > [2] https://lwn.net/Articles/760650/
> >
> > Best regards,
> > Keiichi
> >
> > > Please note that the spec is not finalized yet and a major update is now
> > > discussed with upstream and the Chrome OS team, which is also interested
> > > and deeply involved in the process. The update mostly implies some
> > > rewording and reorganization of data structures, but for sure will
> > > require a driver rework.
> > >
> > > Best regards,
> > > Dmitry.
> > >
> > > On Samstag, 9. Mai 2020 16:11:43 CEST Saket Sinha wrote:
> > > > Hi,
> > > >
> > > > As suggested on #qemu-devel IRC channel, I am including virtio-dev,
> > > > Gerd and Michael to point in the right direction how to move forward
> > > > with Qemu support for Virtio Video V4L2 driver
> > > > posted in [1].
> > > >
> > > > [1]: https://patchwork.linuxtv.org/patch/61717/
> > > >
> > > > Regards,
> > > > Saket Sinha
> > > >
> > > > On Sat, May 9, 2020 at 1:09 AM Saket Sinha <saket.sinha89@gmail.com>
wrote:
> > > > > Hi ,
> > > > >
> > > > > This is to inquire about Qemu support for Virtio Video V4L2 driver
> > > > > posted in [1].
> > > > > I am currently not aware of any upstream effort for Qemu reference
> > > > > implementation and would like to discuss how to proceed with the
> > > > > same.
> > > > >
> > > > > [1]: https://patchwork.linuxtv.org/patch/61717/
> > > > >
> > > > > Regards,
> > > > > Saket Sinha
> > >
> > > ---------------------------------------------------------------------
> > > 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:[~2020-05-11 14:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 23:09 Qemu Support for Virtio Video V4L2 driver Saket Sinha
2020-05-09 14:09 ` Saket Sinha
2020-05-09 14:11 ` Fwd: " Saket Sinha
2020-05-11 9:40 ` Dmitry Sepp
2020-05-11 10:20 ` [virtio-dev] " Keiichi Watanabe
2020-05-11 11:05 ` Saket Sinha
2020-05-11 11:25 ` Dmitry Sepp [this message]
2020-05-11 11:32 ` Michael S. Tsirkin
2020-05-11 11:34 ` Michael S. Tsirkin
2020-05-11 11:49 ` Keiichi Watanabe
2020-05-11 12:32 ` Saket Sinha
2020-05-11 14:06 ` Keiichi Watanabe
2020-05-11 14:31 ` [libcamera-devel] " Laurent Pinchart
2020-05-12 12:10 ` Dmitry Sepp
2020-05-14 23:38 ` Nicolas Dufresne
2020-05-19 8:37 ` Keiichi Watanabe
2020-05-19 17:29 ` Nicolas Dufresne
2020-05-20 3:19 ` Alexandre Courbot
2020-05-20 16:21 ` Nicolas Dufresne
2020-05-20 16:27 ` Michael S. Tsirkin
2020-05-20 16:56 ` Nicolas Dufresne
2020-05-21 7:08 ` Alexandre Courbot
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=2515515.r9knKAEANn@os-lin-dmo \
--to=dmitry.sepp@opensynergy.com \
--cc=Kiran.Pawar@opensynergy.com \
--cc=acourbot@chromium.org \
--cc=alexlau@chromium.org \
--cc=hverkuil@xs4all.nl \
--cc=keiichiw@chromium.org \
--cc=kraxel@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mst@redhat.com \
--cc=posciak@chromium.org \
--cc=qemu-devel@nongnu.org \
--cc=saket.sinha89@gmail.com \
--cc=samiullah.khawaja@opensynergy.com \
--cc=tfiga@chromium.org \
--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 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).