Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Dmitry Sepp <dmitry.sepp@opensynergy.com>
To: Keiichi Watanabe <keiichiw@chromium.org>
Cc: virtio-dev@lists.oasis-open.org,
	"Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Alexandre Courbot" <acourbot@chromium.org>,
	"Alex Lau" <alexlau@chromium.org>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Dylan Reid" <dgreid@chromium.org>,
	"Enrico Granata" <egranata@google.com>,
	"Frediano Ziglio" <fziglio@redhat.com>,
	"Hans Verkuil" <hverkuil@xs4all.nl>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Stéphane Marchesin" <marcheu@chromium.org>,
	"Pawel Osciak" <posciak@chromium.org>,
	spice-devel@lists.freedesktop.org,
	"David Stevens" <stevensd@chromium.org>,
	"Tomasz Figa" <tfiga@chromium.org>,
	uril@redhat.com
Subject: [virtio-dev] Re: [PATCH v2 1/1] virtio-video: Add virtio video device specification
Date: Fri, 20 Dec 2019 16:46:04 +0100	[thread overview]
Message-ID: <2584386.DF4NACHtsB@os-lin-dmo> (raw)
In-Reply-To: <CAD90VcZU_jkY=wZ21R_abTnO8BrL_Sf4AO4Rfz3NP5xZMwmaHA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4039 bytes --]

Hi Keiichi,

On Freitag, 20. Dezember 2019 16:26:50 CET Keiichi Watanabe wrote:
> Hi Dmitry,
> Thanks for the feedback.
> 
> On Thu, Dec 19, 2019 at 10:28 PM Dmitry Sepp
> 
> <dmitry.sepp@opensynergy.com> wrote:
> > Hi Keiichi,
> > 
> > Thank you for the update. Please see some comments below.
> > 
> > Also, we need to bring the virtio_video_control back as it is in fact used
> > by the driver to enumerate supported encoder controls. But yes, it still
> > needs to be documemnted, it's true.
> 
> Yeah, we need it eventually, but I'm wondering what is the difference
> between values set by SET_PARAMS and ones by controls.
> I saw your driver implementation has BITRATE, PROFILE and LEVEL as
> controls. What's the reason why you didn't add them in
> virtio_video_params?
> 

In fact I think the reasons was not to blow up the params structure. Also, 
virtio_video_param is used to inform the driver about the supported controls, very much 
like frame_formats, frame_sizes and so on. But for setting we probably can use the 
set_params structure, right.

> > On Mittwoch, 18. Dezember 2019 14:02:14 CET Keiichi Watanabe wrote:
> > > From: Dmitry Sepp <dmitry.sepp@opensynergy.com>
> > > 
> > > The virtio video encoder device and decoder device provide
> > > functionalities
> > > to encode and decode video stream respectively.
> > > Though video encoder and decoder are provided as different devices, they
> > > use a same protocol.
> > > 
> > > Signed-off-by: Dmitry Sepp <dmitry.sepp@opensynergy.com>
> > > Signed-off-by: Keiichi Watanabe <keiichiw@chromium.org>
> > > ---
> > > 
> > >  content.tex      |   1 +
> > >  virtio-video.tex | 579 +++++++++++++++++++++++++++++++++++++++++++++++
> > >  2 files changed, 580 insertions(+)
> > >  create mode 100644 virtio-video.tex
> > > 
> > > diff --git a/content.tex b/content.tex
> > > index 556b373..9e56839 100644
> > > --- a/content.tex
> > > +++ b/content.tex
> > > @@ -5743,6 +5743,7 @@ \subsubsection{Legacy Interface: Framing
> > > Requirements}\label{sec:Device \input{virtio-vsock.tex}
> > > 
> > >  \input{virtio-fs.tex}
> > >  \input{virtio-rpmb.tex}
> > > 
> > > +\input{virtio-video.tex}
> > > 
> > >  \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
> > > 
> > > diff --git a/virtio-video.tex b/virtio-video.tex
> > > new file mode 100644
> > > index 0000000..30e728d
> > > --- /dev/null
> > > +++ b/virtio-video.tex
> > > @@ -0,0 +1,579 @@
> > > +\section{Video Device}\label{sec:Device Types / Video Device}
> > > +
> > > +The virtio video encoder device and decoder device are virtual devices
> > > that +supports encoding and decoding respectively. Though the encoder
> > > and the decoder +are different devices, they use the same protocol.
> > > +
> > > +\subsection{Device ID}\label{sec:Device Types / Video Device / Device
> > > ID}
> > > +
> > > +\begin{description}
> > > +\item[30] encoder device
> > > +\item[31] decoder device
> > > +\end{description}
> > > +
> > > +\subsection{Virtqueues}\label{sec:Device Types / Video Device /
> > > Virtqueues} +
> > > +\begin{description}
> > > +\item[0] controlq - queue for sending control commands.
> > > +\item[1] eventq - queue for sending events happened in the device.
> > > +\end{description}
> > > +
> > > +\subsection{Feature bits}\label{sec:Device Types / Video Device /
> > > Feature
> > > bits} +
> > > +\begin{description}
> > > +\item[VIRTIO_VIDEO_F_RESOURCE_GUEST_PAGES (0)] Guest pages can be used
> > > for
> > > video +  buffers.
> > > +\end{description}
> > > +
> > > +\devicenormative{\subsubsection}{Feature bits}{Device Types / Video
> > > Device
> > > / Feature bits} +
> > > +The device MUST offer at least one of feature bits.
> > > +
> > > +\subsection{Device configuration layout}\label{sec:Device Types / Video
> > > Device / Device configuration layout} +
> > > +Video device configuration uses the following layout structure:
> > > +
> > > +\begin{lstlisting}
> > > +struct virtio_video_config {
> > > +        le32 max_cap_len;
> > > +};
> > > +\end{lstlisting}
> > > +

[-- Attachment #2: Type: text/html, Size: 131097 bytes --]

  reply	other threads:[~2019-12-20 15:46 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 13:02 [virtio-dev] [PATCH v2 0/1] VirtIO video device specification Keiichi Watanabe
2019-12-18 13:02 ` [virtio-dev] [PATCH v2 1/1] virtio-video: Add virtio " Keiichi Watanabe
2019-12-18 13:40   ` [virtio-dev] " Gerd Hoffmann
2019-12-18 14:08     ` Tomasz Figa
2019-12-19  7:46       ` Gerd Hoffmann
2019-12-19  9:48         ` Dmitry Sepp
2019-12-19  9:59           ` Tomasz Figa
2019-12-19 10:54             ` Dmitry Sepp
2019-12-19 12:05               ` Tomasz Figa
2019-12-19 13:12               ` Gerd Hoffmann
2020-01-08 13:52                 ` Keiichi Watanabe
2020-01-09 13:40                   ` Gerd Hoffmann
2020-01-09 14:20                   ` Tomasz Figa
2020-01-14  7:18                     ` Keiichi Watanabe
2020-01-14 10:35                       ` Dmitry Sepp
2020-01-15  7:49                         ` Keiichi Watanabe
2020-01-15 11:12                         ` Tomasz Figa
2019-12-19 13:01           ` Gerd Hoffmann
2020-01-08 13:50             ` Keiichi Watanabe
2019-12-19  9:26     ` Dmitry Sepp
2019-12-19  9:59       ` Tomasz Figa
2019-12-19 12:54       ` Gerd Hoffmann
2019-12-19 13:28   ` Dmitry Sepp
2019-12-20 15:26     ` Keiichi Watanabe
2019-12-20 15:46       ` Dmitry Sepp [this message]
2019-12-21  6:46         ` Tomasz Figa
2019-12-30 12:16     ` Dmitry Sepp
2020-01-06  6:31       ` Tomasz Figa
2020-01-06  8:33         ` Gerd Hoffmann
2020-01-06  9:29           ` Dmitry Sepp
     [not found]   ` <718815324.16531975.1576690180746.JavaMail.zimbra@redhat.com>
2019-12-20 14:05     ` Keiichi Watanabe
2019-12-20 15:33       ` Dmitry Sepp
2020-01-03 15:47   ` Dmitry Sepp
2020-01-06  8:47     ` Gerd Hoffmann
2020-01-06 10:21     ` Keiichi Watanabe
2020-01-06 14:59   ` Dmitry Sepp
2020-01-07 13:24     ` Keiichi Watanabe
2020-01-07 16:50       ` Dmitry Sepp
2020-01-08  6:59         ` Keiichi Watanabe
2020-01-08 10:00           ` Dmitry Sepp
2020-01-08 12:14             ` Keiichi Watanabe
2020-01-08 12:46               ` Tomasz Figa
2020-01-08 13:05                 ` Keiichi Watanabe
2020-01-08 13:11                 ` Dmitry Sepp
2020-01-08 13:23                   ` Keiichi Watanabe
2020-01-08 12:23   ` Keiichi Watanabe
2019-12-20 15:58 ` [virtio-dev] Re: [PATCH v2 0/1] VirtIO " Dmitry Sepp
2019-12-21  4:36   ` Keiichi Watanabe
2019-12-21  6:18     ` Tomasz Figa
2019-12-21  6:19       ` Tomasz Figa
2020-01-03 13:05         ` Dmitry Sepp
2020-01-06 10:30           ` Keiichi Watanabe
2020-01-06 11:28             ` Dmitry Sepp
2020-01-07 10:25               ` Keiichi Watanabe
2020-01-09 14:56                 ` Dmitry Sepp
2020-01-10 10:16                   ` Dmitry Sepp
2020-01-10 13:53                     ` Keiichi Watanabe
2020-01-10 15:11                       ` Dmitry Sepp
2020-01-11 16:06                         ` Tomasz Figa
2020-01-13  9:50                           ` Dmitry Sepp
2020-01-15 11:23                             ` Keiichi Watanabe
2020-01-13  9:56                         ` Gerd Hoffmann
2020-01-13 10:41                           ` Dmitry Sepp
2020-01-13 11:05                             ` Gerd Hoffmann
2020-01-13 11:59                               ` Tomasz Figa
2020-01-13 13:26                                 ` Gerd Hoffmann
2020-01-15 11:00                                   ` Tomasz Figa
2020-01-15 11:23                                     ` Keiichi Watanabe
2020-01-15 11:26                                     ` Gerd Hoffmann
2020-01-20  7:20                                       ` Keiichi Watanabe
2020-01-20 10:47                                         ` Gerd Hoffmann
2020-01-21  2:47                                           ` Keiichi Watanabe
2020-01-21  6:44                                             ` Gerd Hoffmann
2020-01-21  8:56                                               ` Keiichi Watanabe

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=2584386.DF4NACHtsB@os-lin-dmo \
    --to=dmitry.sepp@opensynergy.com \
    --cc=acourbot@chromium.org \
    --cc=alexlau@chromium.org \
    --cc=daniel@ffwll.ch \
    --cc=dgreid@chromium.org \
    --cc=egranata@google.com \
    --cc=fziglio@redhat.com \
    --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=spice-devel@lists.freedesktop.org \
    --cc=stevensd@chromium.org \
    --cc=tfiga@chromium.org \
    --cc=uril@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox