From: Gerd Hoffmann <kraxel@redhat.com>
To: "Kasireddy, Vivek" <vivek.kasireddy@intel.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Zhang, Tina" <tina.zhang@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Kim, Dongwon" <dongwon.kim@intel.com>
Subject: Re: [PATCH 00/11] Add support for Blob resources feature
Date: Wed, 14 Apr 2021 11:45:02 +0200 [thread overview]
Message-ID: <20210414094502.krykle6fcv2ehkvg@sirius.home.kraxel.org> (raw)
In-Reply-To: <58a1404f12d9434bae1d336f6553279e@intel.com>
Hi,
> Any other ideas as to how to eliminate that Blit cleanly?
Well, "cleanly" pretty much implies "supported by toolkit".
gtk glarea for example sets up a framebuffer and expects the application
render to that framebuffer. So qemu glarea code does a fb-to-fb blit.
Other reasons are scaling and cursor rendering. Not all reasons apply
to all UIs. I think when using spice qemu doesn't blit (not fully sure
what happens inside spice-server), but it could very well be that the
spice-client does the blit instead, i.e. we just shift the issue to
another place ...
take care,
Gerd
next prev parent reply other threads:[~2021-04-14 9:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 3:09 [PATCH 00/11] Add support for Blob resources feature Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 01/11] ui: Get the fd associated with udmabuf driver Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 02/11] ui/pixman: Add qemu_pixman_to_drm_format() Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 03/11] virtio-gpu: Add udmabuf helpers Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 04/11] virtio-gpu: Add virtio_gpu_find_check_resource Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 05/11] virtio-gpu: Refactor virtio_gpu_set_scanout Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 06/11] virtio-gpu: Refactor virtio_gpu_create_mapping_iov Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 07/11] virtio-gpu: Add initial definitions for blob resources Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 08/11] virtio-gpu: Add virtio_gpu_resource_create_blob Vivek Kasireddy
2021-03-31 3:09 ` [PATCH 09/11] virtio-gpu: Add helpers to create and destroy dmabuf objects Vivek Kasireddy
2021-03-31 3:10 ` [PATCH 10/11] virtio-gpu: Add virtio_gpu_set_scanout_blob Vivek Kasireddy
2021-03-31 3:10 ` [PATCH 11/11] virtio-gpu: Update cursor data using blob Vivek Kasireddy
2021-03-31 3:45 ` [PATCH 00/11] Add support for Blob resources feature no-reply
2021-03-31 5:18 ` Zhang, Tina
2021-04-13 6:10 ` Kasireddy, Vivek
2021-04-14 9:45 ` Gerd Hoffmann [this message]
2021-04-14 21:26 ` Kasireddy, Vivek
2021-04-15 7:43 ` Gerd Hoffmann
2021-04-16 6:33 ` Kasireddy, Vivek
2021-04-16 7:56 ` Gerd Hoffmann
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=20210414094502.krykle6fcv2ehkvg@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tina.zhang@intel.com \
--cc=vivek.kasireddy@intel.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).