diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-07 11:09:06 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-07 11:09:06 -0400 |
| commit | 588d43e93d0be54be6d5d6822d78a12b965afadf (patch) | |
| tree | 5e2732d092c198ff605cadff7b9629c3f81c58d5 /tools/guest-diag | |
| parent | ab6fed7ee35a114541373af90184acde9bd94b6b (diff) | |
| download | open-iov-588d43e93d0be54be6d5d6822d78a12b965afadf.tar.gz open-iov-588d43e93d0be54be6d5d6822d78a12b965afadf.zip | |
vgsp: m81 - map the PM ctx-buffer booking VA before the engine context load
The m80 window shows PGRAPH_INTR=0x00000010 (ILLEGAL_METHOD, the reserved-SW
prelude methods, same as the real driver) clearing, then 0x00200002
(SEMAPHORE|EXCEPTION) pending exactly when the QMD activates, followed by the
FECS save/unload. The real driver's launch transient carries the same
ILLEGAL_METHOD without ever setting EXCEPTION, so the exception is the
ctx-restore difference. The one R1-booked ctx VA with no PTE is PM
(0x2370000): the golden9 range mapping covers PATCH/FECS/PRIV/UNR and the four
globals (windows 17..22 after the golden9k 1->6 extension) but never PM, and
R1-before-F2 makes the image carry that VA as the PM pointer. Map it through
the ctx PT window right after the mode-35 PM FBMEM allocation, before any
engine context load and before the PTE line's first fetch.
Diffstat (limited to 'tools/guest-diag')
0 files changed, 0 insertions, 0 deletions
