Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable.
1. Set MUTTER_DEBUG=kms in /etc/environment
2. Enable VRR (TODO: need to relearn all the steps required)
3. Reboot.
4. Log into a Wayland session.
5. Open Google Chrome, start an animation like https://www.vsynctester.com/ and make it full screen (F11).
6. journalctl -f /usr/bin/gnome-shell | grep Post
7. Verify the "Post" messages you see mention direct scan out and not "composite".
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Impact ]
Fullscreen direct scanout is not used if you enable the hidden experimental VRR feature in Mutter 46.
[ Test Plan ]
0. Find a monitor that is VRR capable. /www.vsyncteste r.com/ and make it full screen (F11). gnome-shell | grep Post
1. Set MUTTER_DEBUG=kms in /etc/environment
2. Enable VRR (TODO: need to relearn all the steps required)
3. Reboot.
4. Log into a Wayland session.
5. Open Google Chrome, start an animation like https:/
6. journalctl -f /usr/bin/
7. Verify the "Post" messages you see mention direct scan out and not "composite".
[ Where problems could occur ]
Since the fix affects the runtime decision of whether to allow triple buffering or stay double buffering, the main risk is that triple buffering wouldn't be used in some situation where we would rather have it to maintain a smoother frame rate.
[ Other Info ]
First reported upstream in: /gitlab. gnome.org/ GNOME/mutter/ -/merge_ requests/ 1441#note_ 2062222
https:/
We DO NOT recommend enabling the VRR feature anyway because it is still buggy: /gitlab. gnome.org/ GNOME/mutter/ -/issues/ 3419
https:/