From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v3 12/12] ui/console: call gfx_switch() even if the current scanout is GL
Date: Mon, 7 Mar 2022 21:24:00 +0900 [thread overview]
Message-ID: <d7df9ba7-40db-7b2a-63d7-eacf811da4f2@gmail.com> (raw)
In-Reply-To: <CAMxuvaz3+ySgiOxawVT=P7x4ikDcap0o5Ux78_HdewL0XXa5Kg@mail.gmail.com>
On 2022/03/07 20:50, Marc-André Lureau wrote:
> Hi
>
> On Mon, Mar 7, 2022 at 2:35 PM Akihiko Odaki <akihiko.odaki@gmail.com> wrote:
>>
>> On 2022/03/07 19:19, Marc-André Lureau wrote:
>>> Hi Akihiko
>>>
>>> On Mon, Mar 7, 2022 at 12:09 PM Akihiko Odaki <akihiko.odaki@gmail.com> wrote:
>>>>
>>>> On 2022/03/07 16:46, marcandre.lureau@redhat.com wrote:
>>>>> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>>>>>
>>>>> egl-headless depends on the backing surface to be set before texture are
>>>>> set and updated. Display it (update=true) iff the current scanout kind
>>>>> is SURFACE.
>>>>
>>>> egl-headless does not dynamically call register_displaychangelistener
>>>> and has console associated (console_select would not affect egl-headless
>>>> itself) so this should not be necessary.
>>>
>>> Could you help me understand, what should not be necessary?
>>
>> I read the description as it sets the backing surface for egl-headless
>> when register_displaychangelistener or console_select is called. The
>> change is not necessary.
>
> Without it, gfx_switch is not called to set the new surface. Switching
> console with VNC would fail (via ctrl+alt+num).
Yes, but that is not because egl-headless requires its dpy_gfx_switch to
be called. It is because vnc does not receive the surface. The patch
adds a call of dpy_gfx_switch no matter if the receiver is an OpenGL
display or not, but an OpenGL display would not need one.
>
>>
>>>
>>>> The remaining problem with egl-headless is that egl-headless renders the
>>>> image to DisplaySurface, and a non-OpenGL display (namely vnc) has to
>>>> consume it instead of texture even when con->scanout.kind is
>>>> SCANOUT_TEXTURE or SCANOUT_DMABUF.
>>>
>>> This is already happening, because egl-headless calls dpy_gfx_update().
>>
>> It is not called when register_displaychangelistener or console_select
>> is called by non-OpenGL display consuming the DisplaySurface.
>
> When displaychangelistener_display_console() is called with
> con->scanount.kind == SCANOUT_SURFACE, it calls gfx_update(update ==
> TRUE), and thus calls gfx_update on the whole surface.
>
con->scanout.kind is SCANOUT_TEXTURE or SCANOUT_DMABUF when egl-headless
is rendering to surface. It would not call gfx_update in the case.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2022-03-07 12:27 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 7:46 [PATCH v3 00/12] GL & D-Bus display related fixes marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 01/12] ui/console: move check for compatible GL context marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 02/12] ui/console: move dcl compatiblity check to a callback marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 03/12] ui/console: egl-headless is compatible with non-gl listeners marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 04/12] ui/dbus: associate the DBusDisplayConsole listener with the given console marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 05/12] ui/console: move console compatibility check to dcl_display_console() marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 06/12] ui/shader: fix potential leak of shader on error marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 07/12] ui/shader: free associated programs marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 08/12] ui/console: add a dpy_gfx_switch callback helper marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 09/12] ui/console: optionally update after gfx switch marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 10/12] ui/dbus: fix texture sharing marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 11/12] ui/dbus: do not send 2d scanout until gfx_update marcandre.lureau
2022-03-07 7:46 ` [PATCH v3 12/12] ui/console: call gfx_switch() even if the current scanout is GL marcandre.lureau
2022-03-07 8:08 ` Akihiko Odaki
2022-03-07 10:19 ` Marc-André Lureau
2022-03-07 10:34 ` Akihiko Odaki
2022-03-07 11:50 ` Marc-André Lureau
2022-03-07 12:24 ` Akihiko Odaki [this message]
2022-03-07 12:32 ` Marc-André Lureau
2022-03-07 12:49 ` Akihiko Odaki
2022-03-08 14:26 ` Marc-André Lureau
2022-03-08 14:42 ` Akihiko Odaki
2022-03-09 8:02 ` Marc-André Lureau
2022-03-09 8:05 ` Akihiko Odaki
2022-03-09 8:11 ` Marc-André Lureau
2022-03-09 8:21 ` Akihiko Odaki
2022-03-09 8:33 ` Marc-André Lureau
2022-03-09 8:34 ` Akihiko Odaki
2022-03-09 8:40 ` Marc-André Lureau
2022-03-09 8:49 ` Akihiko Odaki
2022-03-09 8:54 ` Marc-André Lureau
2022-03-09 9:02 ` Akihiko Odaki
2022-03-09 9:26 ` Gerd Hoffmann
2022-03-09 9:32 ` Akihiko Odaki
2022-03-09 9:53 ` Marc-André Lureau
2022-03-09 10:01 ` Akihiko Odaki
2022-03-09 10:07 ` Marc-André Lureau
2022-03-09 10:20 ` Akihiko Odaki
2022-03-09 10:27 ` Marc-André Lureau
2022-03-09 10:38 ` Akihiko Odaki
2022-03-09 10:45 ` Marc-André Lureau
2022-03-09 10:54 ` Akihiko Odaki
2022-03-09 10:13 ` Gerd Hoffmann
2022-03-09 10:15 ` [PATCH v3 00/12] GL & D-Bus display related fixes 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=d7df9ba7-40db-7b2a-63d7-eacf811da4f2@gmail.com \
--to=akihiko.odaki@gmail.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).