[fcui-amd]

Motivation

MemoryAccessCoherentTest enqueues a barrier-AND packet and a kernel dispatch, then rings the queue doorbell so a host-to-device copy, the shader, and a device-to-host copy run in order. The barrier header was published with the packet body, and the doorbell was rung with the queue write index after both packets had already advanced it. The command processor can then see an incomplete barrier packet or a doorbell value one slot past the last written packet, so the coherent copy sequence does not complete.

Technical Details

• The barrier-AND packet is copied into the queue with its header still invalid. rocrtst::AtomicSetPacketHeader then release-stores the packet type, matching the dispatch path and GPUAccessToCPUMemoryTest in the same file.
• The kernel-dispatch slot is kept in dispatch_index. The doorbell is stored with that index, the last packet written, instead of a write index reloaded after the queue has already been advanced past it.

Issue Tracking

Test Plan

Run the rocrtst memory-access functional suite and confirm MemoryAccessCoherentTest completes

Test Result

Submission Checklist

• Look over the contributing guidelines at https://github.com/ROCm/rocm-systems/blob/develop/CONTRIBUTING.md.

[therock-pr-bot]

❌ PR Check — Action Required

Check	Status	Details
📝 PR Description	❌ Fail	Error: PR description must reference a JIRA ID, ISSUE ID, or a GitHub closing keyword. Expected: include a JIRA ID / ISSUE ID line (separator : or -, or omitted; value may be a JIRA key, a number with/without #, or a link), OR a closing keyword + issue reference. Accepted examples: • JIRA ID : TESTAUTO-6039 • JIRA ID - #330 • JIRA ID #330 • JIRA ID (on separate line) ROCM-25757 • ISSUE ID : TESTUTO-3334 • ISSUE ID #3334 • ISSUE ID - TESTAUTO-3433 • ISSUE ID (on separate line) AIRUNTIME-2352 • ISSUE ID : https://github.com/<org_name>/<repo_name>/issues/1234 • Closes #10 • Fixes octo-org/octo-repo#100 • Resolves: #123 • #123 • https://github.com/<org_name>/<repo_name>/issues/123 Current: no valid JIRA/ISSUE/closing-keyword reference found
⛔ Forbidden Files	✅ Pass	—
🧪 Unit Test	⚠️ Warning	Error: Source/code files changed without an accompanying unit test. Expected: add at least one test file named like test_<name>.py / test_<name>.cpp (or <name>_test.*). Current: code file(s) changed: projects/rocr-runtime/rocrtst/suites/functional/memory_access.cc; no test file found
🔎 pre-commit	⏳ Pending	⏳ Still running…
🚫 Draft PR	🔜 To Be Enabled	—
🚩 Feature Flag	🔜 To Be Enabled	—
📊 Code Coverage	🔜 To Be Enabled	—

⚠️ 1 policy check(s) failed. Please address the issues above before this PR can be Reviewed.

🚫 Please fix the failed policies

• ❌ PR Description

The Not ready to Review label was added to this PR. Once all policies pass, the label is removed automatically.

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

🙋 Wish to Override Policy?

[therock-pr-bot]

🚫 Please fix the failed policies before requesting reviews.

The following policy checks failed:

• ❌ PR Description

The Not ready to Review label has been added to this PR.
Once all policies pass, the label will be removed automatically.

[fcui-amd]

ping?

[shwetagkhatri]

LGTM

[systems-assistant]

TheRock Submodule Bump Activity

Newest first

• 2026-11-05 — Included in TheRock via ROCm/TheRock#9739.