Skip to content

mesa-aurora: pin omacom/mesa#20 for G17P memory-scope flushes - #1931

Merged
ryanrhughes merged 1 commit into
omacom:masterfrom
scottjones:mesa-aurora-pin-mesa20
Oct 31, 2026
Merged

ryanrhughes merged 1 commit into
omacom:masterfrom
scottjones:mesa-aurora-pin-mesa20

Conversation

@scottjones

Copy link
Copy Markdown
Contributor

Pins mesa-aurora to integration/aurora at a1969111 (omacom/mesa#20). It gives G17P (Neo) host-read and aliased-memory flushes memory scope, which fixes the stale reads queue.depth and sparse.churn hit. The behaviour change is limited to G17P barriers and events; other chips only gain a counter.

We checked omacom/mesa#20 on a Neo with a private driver built at 18ff4cdc9a, on a kernel with the G17 queue stack: queue.depth 5/5 and sparse.churn 3/3 with no kernel-log flags. Everything from that commit to this pin is comments in hk_device.h. On the known-good kernel, queue.depth loses the device, a kernel stall this doesn't touch. This pin itself is untested on aurora12.

Still open:

Test plan

  • The package builds and publishes to edge for aarch64
  • Neo: queue.depth and sparse.churn on this package, on aurora12
  • Neo: CTS synchronization lists, not yet run on this branch
  • Neo: Zink A/B
  • M1, M2, M3: desktop and Vulkan smoke test on this package

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ryanrhughes
ryanrhughes enabled auto-merge (squash) October 31, 2026 17:10
@ryanrhughes
ryanrhughes merged commit 73f3284 into omacom:master Oct 31, 2026
7 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

Publish succeeded → live

Packages: mesa-aurora (aarch64, PR artifact)

  • edge/aarch64: mesa-aurora-1:26.3.0_devel.20261031.231483.a1969111475-1-aarch64, vulkan-aurora-1:26.3.0_devel.20261031.231483.a1969111475-1-aarch64

Commit 73f3284 · run

stevederico pushed a commit to stevederico/omarchy-pkgs that referenced this pull request Oct 31, 2026
…#1931)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants