mirror of
https://github.com/Droid-Deck/DroidDeck.git
synced 2026-11-22 06:15:58 +00:00
Performance: a switch to keep Steam's xalia helper out of the session
xalia is an x86 Windows program Proton launches to give Windows programs gamepad navigation. Under FEX it cannot load the session's aarch64 preload shim, so its socket() and memfd calls reach the vendor's seccomp filter raw - and where that answers ENOSYS, measured on a Galaxy Fold, it storms: 89 refusals of each in a few seconds, then a broken Wayland pipe and a session that is gone 6-12 seconds after Big Picture appeared. Fourteen sessions in eighteen minutes died that way on one device while the same build ran for minutes on another. Proton has its own gate for it, PROTON_USE_XALIA, so the switch sets that rather than interfering with the helper. Off by default: xalia is Valve's, and on a device whose seccomp answers its syscalls normally there is no reason to take it away.
This commit is contained in:
1 parent
d7038a2b50
commit
13c512de0b
5 files changed
+44
-5
No files matched your search
@@ -214,8 +214,13 @@ separate because they are wanted at the same time and suit different things:
|
||||
|
||||
Both apply at the next session start.
|
||||
|
||||
Under the same dialog, two **driver tunables** for a runtime that renders slowly, tried one at a
|
||||
time: **Turnip: sysmem rendering** (`TU_DEBUG=sysmem`, Banners-Turnip's advice for an Adreno 8xx that
|
||||
Under the same dialog, **session fixes** for a device the runtime does not sit well on, tried one at
|
||||
a time. **Skip Steam's xalia helper** (`PROTON_USE_XALIA=0`) is the one to reach for when a session
|
||||
dies seconds after Big Picture appears: xalia is an x86 Windows program Proton starts for gamepad
|
||||
navigation, it cannot load the session's preload shim under FEX, and where the vendor's seccomp
|
||||
answers its `socket()` and `memfd` calls with ENOSYS it storms until the session collapses (89
|
||||
refusals then a broken pipe, in the log). It costs gamepad navigation in Windows programs that are
|
||||
not games. Then two for a runtime that renders slowly: **Turnip: sysmem rendering** (`TU_DEBUG=sysmem`, Banners-Turnip's advice for an Adreno 8xx that
|
||||
looks glitchy or slow; a 710/720/722 gets it on its own) and **Zink: lazy descriptors**
|
||||
(`ZINK_DESCRIPTORS=lazy`, for Steam's menus, which Chromium draws through Zink — the first thing to
|
||||
try when they are slow while games are fast). The `steamdeck-tu-debug` and `steamdeck-env` files in
|
||||
|
||||
Reference in new issue
Block a user