From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Bilal Elmoussaoui <belmouss@redhat.com>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
chergert@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH] ui/dbus: Implement damage regions for GL
Date: Tue, 9 May 2023 16:33:34 +0200 [thread overview]
Message-ID: <00958ee1-4c47-20e9-bcd0-ed92179ee831@linaro.org> (raw)
In-Reply-To: <20230509115940.114033-1-belmouss@redhat.com>
Hi,
On 9/5/23 13:59, Bilal Elmoussaoui wrote:
> From: Christian Hergert <chergert@redhat.com>
>
> Currently, when using `-display dbus,gl=on` all updates to the client
> become "full scanout" updates, meaning there is no way for the client to
> limit damage regions to the display server.
>
> Instead of using an "update count", this patch tracks the damage region
> and propagates it to the client.
>
> This was less of an issue when clients were using GtkGLArea for
> rendering,
> as you'd be doing full-surface redraw. To be efficient, the client needs
> both a DMA-BUF and the damage region to be updated.
>
> In the future, when additional methods are allowed on the D-Bus
> interface,
> this should likely be updated to send damage regions as a single RPC to
> avoid additional message processing.
>
> Currently, Linux does not propagate damage rectangles when using the
> virtio-gpu drm driver. That means compositors such as Mutter which
> utilize
> drmModePageFlip() will be sending full or near-full surface damages.
>
> https://lists.freedesktop.org/archives/dri-devel/2023-March/395164.html
> contains a patch to fix that too.
>
> Signed-off-by: Bilal Elmoussaoui <belmouss@redhat.com>
> ---
> meson.build | 8 ++++++++
> ui/dbus-listener.c | 25 +++++++++++++++++++------
> ui/meson.build | 2 +-
> 3 files changed, 28 insertions(+), 7 deletions(-)
>
> diff --git a/meson.build b/meson.build
> index 229eb585f7..72678ef78e 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -1761,6 +1761,14 @@ dbus_display = get_option('dbus_display') \
> error_message: '-display dbus is not available on Windows') \
> .allowed()
^ dbus strictly required deps, ...
> +cairo = not_found
> +if dbus_display
> + cairo = dependency('cairo',
> + kwargs: static_kwargs,
> + method: 'pkg-config',
> + )
cairo declared as optional dep, ...
> +endif
> +
> have_virtfs = get_option('virtfs') \
> .require(targetos == 'linux' or targetos == 'darwin',
> error_message: 'virtio-9p (virtfs) requires Linux or macOS') \
> diff --git a/ui/dbus-listener.c b/ui/dbus-listener.c
> index 911acdc529..047be5cb3a 100644
> --- a/ui/dbus-listener.c
> +++ b/ui/dbus-listener.c
> @@ -25,6 +25,7 @@
> #include "qemu/error-report.h"
> #include "sysemu/sysemu.h"
> #include "dbus.h"
> +#include <cairo.h>
cairo used unconditionally.
Shouldn't we now declared it as a strict dependency in meson?
> #include <gio/gunixfdlist.h>
>
> #ifdef CONFIG_OPENGL
next prev parent reply other threads:[~2023-05-09 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 11:59 [PATCH] ui/dbus: Implement damage regions for GL Bilal Elmoussaoui
2023-05-09 14:33 ` Philippe Mathieu-Daudé [this message]
2023-05-09 15:04 ` Bilal Elmoussaoui
2023-05-09 15:18 ` Philippe Mathieu-Daudé
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 12:07 [PATCH] ui/dbus: implement " Bilal Elmoussaoui
2023-08-14 12:41 ` Marc-André Lureau
2023-08-14 12:59 ` Bilal Elmoussaoui
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=00958ee1-4c47-20e9-bcd0-ed92179ee831@linaro.org \
--to=philmd@linaro.org \
--cc=belmouss@redhat.com \
--cc=berrange@redhat.com \
--cc=chergert@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).