summaryrefslogtreecommitdiffstats
path: root/tools/guest-diag/wall2/wall2_livecap2.py
diff options
context:
space:
mode:
authorArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-11 21:55:47 -0500
committerArthur Hanson Rasmusson <arthur@vgpu.io>2026-11-11 21:55:47 -0500
commit8c7bf2959c62743899dfdc6097dabfaebf227158 (patch)
tree444714ec225532e02d78b3e49e6f297b004c96df /tools/guest-diag/wall2/wall2_livecap2.py
parent889ccc0f3992022762d4a4d6a3641b64699d5bd3 (diff)
downloadopen-iov-8c7bf2959c62743899dfdc6097dabfaebf227158.tar.gz
open-iov-8c7bf2959c62743899dfdc6097dabfaebf227158.zip
vgsp: report FB info sizes in KB and use 0 for unsupported context buffers
The FB info ABI documents RAM_SIZE/TOTAL_RAM_SIZE/USABLE_RAM_SIZE/HEAP_SIZE/ MAPPABLE_HEAP_SIZE/HEAP_FREE/BAR1_SIZE/BAR1_AVAIL_SIZE in kilobytes; the emulation returned bytes, over-reporting the emulated framebuffer by 1024x to the X DDX. COMPRESSION_SIZE and L2CACHE_SIZE remain in bytes. KGR_GET_CONTEXT_BUFFERS_INFO reported NV_U32_MAX for buffer kinds Turing does not support. kgraphics treats size==0 as unsupported (skip); an NV_U32_MAX byte length rounds up to exactly 4 GiB in the page-count computation, which is the shape of the transient guest sysmem allocations. Report 0/0 instead. Evidence: handoff-meta-plan.md CONT.435 (c15-c21 allocation traces, the guest nvidia.ko disassembly of osAllocPagesInternal), kernel 570.144 ctrl2080fb.h units and kernel_graphics.c:1775-1800.
Diffstat (limited to 'tools/guest-diag/wall2/wall2_livecap2.py')
0 files changed, 0 insertions, 0 deletions