[PATCH xserver 0/4] Rework suspending GLX clients

Keith Packard keithp at keithp.com
Thu Jun 29 17:30:41 UTC 2017

Adam Jackson <ajax at redhat.com> writes:

> As far as I can tell, DRI3 clients do not need to suspend when VT
> switched. Also, the code to drive that suspension is in the wrong
> place, a client that only issued DRI1 requests but not GLX would not be
> slept on VT switch.

I'm not sure I understand why DRI1 and DRI2 clients need to have their X
requests suspended either? Are we using this to get them to stop talking
to the device on the client side?

> This series adds the concept of a VT client to the xfree86 core, sets
> connected DRI1 and DRI2 clients as VT clients, and removes vt tracking
> from the GLX code. There is presently no way to _unset_ a client's
> VT-ness; in the DRI1 case there's no "close DRI connection" request
> anyway. In principle DRI2 clients might not need this either but I'm
> not interested in proving it.

The patches look fine to me; I'm just not understanding what suspending
X processing while VT switched was ever supposed to do...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.x.org/archives/xorg-devel/attachments/20170629/89ccbcab/attachment.sig>

More information about the xorg-devel mailing list