testsAndMisc/docs/superpowers/evidence/amd-x3d-vcache-mode-cache-2026-11-12.json
Krzysztof kuhy Rudnicki 32b94bfbd2
Some checks failed
dependency freshness / dependencies on newest stable (push) Has been cancelled
md-naming / markdown naming convention (push) Has been cancelled
Pre-commit checks / pre-commit (${{ matrix.group }}) (mypy, mypy) (push) Has been cancelled
Pre-commit checks / pre-commit (${{ matrix.group }}) (pylint, pylint) (push) Has been cancelled
Pre-commit checks / pre-commit (${{ matrix.group }}) (rest, ) (push) Has been cancelled
Pre-commit checks / pre-commit (${{ matrix.group }}) (shellcheck, shellcheck) (push) Has been cancelled
Python tests / test (push) Has been cancelled
repo-contract / repo contract (push) Has been cancelled
Shell tests / shell-tests (push) Has been cancelled
Shell tests / lib-tests (push) Has been cancelled
Shell tests / arch-tests (push) Has been cancelled
Set AMD X3D V-cache mode to cache via udev
amd_x3d_mode defaulted to frequency, so the scheduler preferred the
non-V-cache CCD. kuhy chose cache: games prefer CPUs 0-5,12-17; background
jobs are already pinned to 6-11,18-23.

A udev rule matches DRIVER amd_x3d_vcache on add (boot coldplug) and bind
(any rebind), so it hard-codes no device name and survives a rebind,
unlike a tmpfiles w line. fixes/fix_amd_x3d_vcache.sh installs it, fires
a synthetic bind event and checks the mode ends on cache. Same layout as
fix_webcam_c270.sh, with a bats test.

Host: mode frequency -> cache, prefcore ranking now favours 0-5,12-17.
vmbox has no X3D device: only the install step was proven there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WzxdWYWDKuhbBAoNETfoB9
2026-11-12 13:03:12 +01:00

39 lines
1.6 KiB
JSON

{
"intent": "AMD X3D V-cache mode is cache on every boot and driver rebind, so the scheduler prefers the V-cache CCD for games.",
"scope": [
"linux_configuration/fixes/60-amd-x3d-vcache-mode.rules",
"linux_configuration/fixes/fix_amd_x3d_vcache.sh",
"linux_configuration/tests/test_fix_amd_x3d_vcache.bats",
"Non-goal: CPU pinning of background jobs (already done)"
],
"changes": [
"udev rule matching DRIVER amd_x3d_vcache on add and bind, no device name",
"Installer with install, --remove and --status, same pattern as fix_webcam_c270.sh"
],
"verification": [
{
"command": "bats linux_configuration/tests/test_fix_amd_x3d_vcache.bats",
"result": "pass",
"evidence": "red while the script was missing; 8 ok after"
},
{
"command": "fixes/fix_amd_x3d_vcache.sh on the host",
"result": "pass",
"evidence": "amd_x3d_mode frequency -> cache; prefcore ranking CPUs 0-5,12-17 now 196-216 vs 6-11,18-23 166-191 (before 166-191 vs 196-216); unbind/bind keeps cache"
},
{
"command": "vm run atomichosts fix_amd_x3d_vcache.sh",
"result": "pass",
"evidence": "installs the rule, udevadm verify clean; no X3D device in vmbox so the mode itself is host-only"
}
],
"risks": [
"Games on the V-cache CCD may boost lower than on the frequency CCD",
"Background load spills onto the V-cache CCD if the pinning is lifted"
],
"rollback": [
"fixes/fix_amd_x3d_vcache.sh --remove, then write frequency to amd_x3d_mode or reboot",
"Check cat /sys/bus/platform/drivers/amd_x3d_vcache/*/amd_x3d_mode"
]
}