public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Morozov <dmitry.morozov@opensynergy.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Tomasz Figa" <tfiga@chromium.org>,
	stevensd@chromium.org, virtio-dev@lists.oasis-open.org,
	"Keiichi Watanabe" <keiichiw@chromium.org>,
	"Alexandre Courbot" <acourbot@chromium.org>,
	alexlau@chromium.org, dgreid@chromium.org,
	"Stéphane Marchesin" <marcheu@chromium.org>,
	"Pawel Osciak" <posciak@chromium.org>,
	"Hans Verkuil" <hverkuil@xs4all.nl>,
	"Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Daniel Vetter" <daniel@ffwll.ch>
Subject: Re: [virtio-dev] [PATCH] [RFC RESEND] vdec: Add virtio video decode device specification
Date: Mon, 14 Oct 2019 15:05:03 +0200	[thread overview]
Message-ID: <12599990.jpbsygJuY9@os-lin-dmo> (raw)
In-Reply-To: <20191014123443.ey3yfdnr43kplqaq@sirius.home.kraxel.org>


On Montag, 14. Oktober 2019 14:34:43 CEST Gerd Hoffmann wrote:
>   Hi,
> 
> > My take on this (for a decoder) would be to allocate memory for output
> > buffers from a secure ION heap, import in the v4l2 driver, and then to
> > provide those to the device using virtio. The device side then uses the
> > dmabuf framework to make the buffers accessible for the hardware. I'm not
> > sure about that, it's just an idea.
> 
> Virtualization aside, how does the complete video decoding workflow
> work?  I assume along the lines of ...
> 
>   (1) allocate buffer for decoded video frames (from ion).
>   (2) export those buffers as dma-buf.
>   (3) import dma-buf to video decoder.
>   (4) import dma-buf to gpu.
> 
> ... to establish buffers shared between video decoder and gpu?
> 
> Then feed the video stream into the decoder, which decodes into the ion
> buffers?  Ask the gpu to scanout the ion buffers to show the video?
> 
> cheers,
>   Gerd

Yes, exactly.

[decoder]
1) Input buffers are allocated using  VIDIOC_*BUFS.
2) Output buffers are allocated in a guest specific manner (ION, gbm).
3) Both input and output buffers are exported as dma-bufs.
4) The backing storage of both inputs and outputs is made available to the 
device.
5) Decoder hardware writes to output buffers directly.
6) Back to the guest side, the output dma-bufs are used by (virtio-) gpu.

Best regards,
Dmitry 



  reply	other threads:[~2019-10-14 13:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19  9:34 [PATCH] [RFC RESEND] vdec: Add virtio video decode device specification Keiichi Watanabe
2019-09-19  9:52 ` Hans Verkuil
2019-09-19 11:15   ` Keiichi Watanabe
2019-09-19 11:17     ` Keiichi Watanabe
2019-09-23  8:56 ` [virtio-dev] " Gerd Hoffmann
2019-10-05  6:08   ` Tomasz Figa
2019-10-07 14:00     ` Dmitry Morozov
2019-10-07 14:14       ` Tomasz Figa
2019-10-07 15:09         ` Dmitry Morozov
2019-10-09  3:55           ` Tomasz Figa
2019-10-11  8:53             ` Dmitry Morozov
2019-10-14 12:34               ` Gerd Hoffmann
2019-10-14 13:05                 ` Dmitry Morozov [this message]
2019-10-15  7:54                   ` Gerd Hoffmann
2019-10-15 14:06                     ` Dmitry Morozov
2019-10-17  8:06                       ` Tomasz Figa
2019-10-17  6:40               ` Tomasz Figa
2019-10-17  7:19                 ` Gerd Hoffmann
2019-10-17  8:11                   ` Tomasz Figa
2019-10-17 10:13                     ` Gerd Hoffmann
2019-10-29  7:39                       ` David Stevens
2019-10-31  7:30                         ` Keiichi Watanabe
2019-10-31  9:10                       ` David Stevens
2019-11-07  8:29                         ` Keiichi Watanabe
2019-10-14 12:19     ` Gerd Hoffmann
2019-10-17  6:58       ` Tomasz Figa
2019-10-17  7:44         ` Gerd Hoffmann
2019-10-17  8:23           ` Tomasz Figa
2019-10-17 10:22             ` Gerd Hoffmann
2019-10-17  7:06       ` David Stevens

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=12599990.jpbsygJuY9@os-lin-dmo \
    --to=dmitry.morozov@opensynergy.com \
    --cc=acourbot@chromium.org \
    --cc=alexlau@chromium.org \
    --cc=daniel@ffwll.ch \
    --cc=dgreid@chromium.org \
    --cc=hverkuil@xs4all.nl \
    --cc=keiichiw@chromium.org \
    --cc=kraxel@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=marcheu@chromium.org \
    --cc=posciak@chromium.org \
    --cc=stevensd@chromium.org \
    --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