summaryrefslogtreecommitdiffstats
path: root/wiki/open-iov.org/load.php?lang=en&modules=ext.visualEditor.desktopArticleTarget.noscript|filep...
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 18:28:19 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-22 18:28:19 -0400
commitdece666732a95bafd349cac2fb2fbcd3aa3afa53 (patch)
tree0714df6561fb075c7d810fe1ff0c9728d22cd06d /wiki/open-iov.org/load.php?lang=en&modules=ext.visualEditor.desktopArticleTarget.noscript|filepage|mediawiki.action.view.filepage|skins.vector.styles.legacy&only=styles&skin=vector.css
parentd03e69b85d4d795222fdf5eae637d7ae763c3702 (diff)
downloadopen-iov-dece666732a95bafd349cac2fb2fbcd3aa3afa53.tar.gz
open-iov-dece666732a95bafd349cac2fb2fbcd3aa3afa53.zip
r496h do not pin a linear window for content-scanned rings; the VAS walk resolves the rest
The registered COPY_SERVER_PDES directory walks the ring VA correctly (trace: L0 -> L1 -> L2 idx 9 -> PD0), but the linear window pin installed around the ring shadows it in svc_lookup_trusted (pin_lookup_any returns the win-flagged entry first), so the pushbuffer/tracker reads kept using the wrong noncontiguous guess. Pin only the content-validated ring page; every other VA of the client now resolves through the walk.
Diffstat (limited to 'wiki/open-iov.org/load.php?lang=en&modules=ext.visualEditor.desktopArticleTarget.noscript|filepage|mediawiki.action.view.filepage|skins.vector.styles.legacy&only=styles&skin=vector.css')
0 files changed, 0 insertions, 0 deletions