From: Vivek Kasireddy <vivek.kasireddy@intel.com>
To: qemu-devel@nongnu.org
Cc: "Vivek Kasireddy" <vivek.kasireddy@intel.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Dongwon Kim" <dongwon.kim@intel.com>
Subject: [RFC v2 0/2] spice: Add an option to forward the dmabuf directly to the encoder (v2)
Date: Mon, 23 Jan 2023 00:37:53 -0800 [thread overview]
Message-ID: <20230123083755.1038286-1-vivek.kasireddy@intel.com> (raw)
This patch series adds options to select a preferred codec and also
to forward a dmabuf directly to the encoder module that is part of
the Spice server. Currently, gstreamer:h264 is the only combination
tested but additional work is ongoing to test other combinations.
Tested with: -device virtio-gpu-pci,max_outputs=1,blob=true,xres=1920,yres=1080
-spice port=3001,gl=on,disable-ticketing=on,dmabuf-encode=on,
preferred-codec=gstreamer:h264
and remote-viewer --spice-debug spice://x.x.x.x:3001 on the client side.
Associated Spice server patches (v1) can be found here:
https://lists.freedesktop.org/archives/spice-devel/2023-January/052927.html
v2:
- Used the already available gl_scanout and gl_draw_async APIs instead
of adding new ones to Spice.
- Improved the commit message of the second patch
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: Marc-André Lureau <marcandre.lureau@redhat.com>
Cc: Dongwon Kim <dongwon.kim@intel.com>
Vivek Kasireddy (2):
spice: Add an option for users to provide a preferred codec
spice: Add an option to forward the dmabuf directly to the encoder
(v2)
include/ui/spice-display.h | 1 +
qemu-options.hx | 11 +++++-
ui/spice-core.c | 36 ++++++++++++++++--
ui/spice-display.c | 75 ++++++++++++++++++++++++++++----------
4 files changed, 100 insertions(+), 23 deletions(-)
--
2.37.2
next reply other threads:[~2023-01-23 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 8:37 Vivek Kasireddy [this message]
2023-01-23 8:37 ` [RFC v2 1/2] spice: Add an option for users to provide a preferred codec Vivek Kasireddy
2023-01-25 10:57 ` Frediano Ziglio
2023-01-23 8:37 ` [RFC v2 2/2] spice: Add an option to forward the dmabuf directly to the encoder (v2) Vivek Kasireddy
2023-01-23 10:06 ` Gerd Hoffmann
2023-01-24 6:41 ` Kasireddy, Vivek
2023-01-24 7:45 ` Gerd Hoffmann
2023-01-25 11:10 ` Frediano Ziglio
2023-01-30 2:24 ` Kasireddy, Vivek
2023-02-01 18:25 ` Frediano Ziglio
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=20230123083755.1038286-1-vivek.kasireddy@intel.com \
--to=vivek.kasireddy@intel.com \
--cc=dongwon.kim@intel.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.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).