summaryrefslogtreecommitdiffstats
path: root/wiki/open-iov.org/index.php/Special:WhatLinksHere/File:Figure_0-_i915_vGPU_Scheduling.png.html
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-12 16:47:30 -0400
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-10-12 16:47:30 -0400
commitbb5397afd7afcb97865508ff8c23963ffcd5334f (patch)
treec0cc61f6a230b0f69c03bf6da871a8949a086a19 /wiki/open-iov.org/index.php/Special:WhatLinksHere/File:Figure_0-_i915_vGPU_Scheduling.png.html
parent54a8f7b3385cccedac3f74a73ae9bc04089203d0 (diff)
downloadopen-iov-master.tar.gz
open-iov-master.zip
guest-diag: keep CE push-buffer latches on stale refresh; never fail freshness on an unknown page PAHEADmaster
Two scanner defects seen in r131: (1) a resolved CE mem whose first vmap page could not be translated at store time stored page_pa=0, and the freshness check then failed on every probe, dropping the latch and re-resolving in a tight loop - and each failed re-resolution left the host with no pins for the channel at all; (2) the stale path discarded the latch before knowing the re-resolution would produce anything. Unknown PA now counts as fresh (the {cpu,gpu} object check is the evidence), and a stale refresh keeps the previous latch unless a new resolution actually emits runs.
Diffstat (limited to 'wiki/open-iov.org/index.php/Special:WhatLinksHere/File:Figure_0-_i915_vGPU_Scheduling.png.html')
0 files changed, 0 insertions, 0 deletions