<feed xmlns='http://www.w3.org/2005/Atom'>
<title>open-iov.git/tools/guest-diag/guest_kprobes.sh, branch gr-forwarding</title>
<subtitle>Open-IOV vGPU-IO: host-side GSP emulation for unmodified NVIDIA guest drivers
</subtitle>
<id>https://git.vgpu.io/open-iov.git/atom?h=gr-forwarding</id>
<link rel='self' href='https://git.vgpu.io/open-iov.git/atom?h=gr-forwarding'/>
<link rel='alternate' type='text/html' href='https://git.vgpu.io/open-iov.git/'/>
<updated>2026-09-30T14:14:09+00:00</updated>
<entry>
<title>guest-diag: mount tracefs before installing kprobes</title>
<updated>2026-09-30T14:14:09+00:00</updated>
<author>
<name>Arthur Hanson Rasmusson</name>
<email>arthur@vgpu.io</email>
</author>
<published>2026-09-30T14:14:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.vgpu.io/open-iov.git/commit/?id=e4f0796024995cd2438bd087fd720aa3597cf4f3'/>
<id>urn:sha1:e4f0796024995cd2438bd087fd720aa3597cf4f3</id>
<content type='text'>
A fresh boot can leave /sys/kernel/tracing as an unmounted mount point;
the probe adds then fail silently (probe count 0) and the whole sem/kptr
pipeline goes blind.
</content>
</entry>
<entry>
<title>guest-diag: enlarge and clear the trace ring at probe install</title>
<updated>2026-09-29T21:31:55+00:00</updated>
<author>
<name>Arthur Hanson Rasmusson</name>
<email>arthur@vgpu.io</email>
</author>
<published>2026-09-29T21:31:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.vgpu.io/open-iov.git/commit/?id=ebf8e34a348a4563f7581b71a0c0f12d20851561'/>
<id>urn:sha1:ebf8e34a348a4563f7581b71a0c0f12d20851561</id>
<content type='text'>
The client's spin floods the default ring with uvmt/uvsv events; a one-shot
uvbp event was overwritten before the pin scanner read it (push-buffer pin
landed ~50 s after the client began pushing). 64 MB ring + clear.
</content>
</entry>
<entry>
<title>guest-diag: probe the tracker completion check and its result</title>
<updated>2026-09-29T21:17:42+00:00</updated>
<author>
<name>Arthur Hanson Rasmusson</name>
<email>arthur@vgpu.io</email>
</author>
<published>2026-09-29T21:17:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.vgpu.io/open-iov.git/commit/?id=feb7769e3ca6b155fb5c76567a25af63bddcc3b6'/>
<id>urn:sha1:feb7769e3ca6b155fb5c76567a25af63bddcc3b6</id>
<content type='text'>
uvsv/uvsvr capture (sem, value) and the boolean return of
uvm_gpu_tracking_semaphore_is_value_completed, so a wait that fails despite
an advanced payload is visible as a false return.
</content>
</entry>
<entry>
<title>guest-diag: probe uvm_tracker_wait_for_entry for the exact (channel, value) wait</title>
<updated>2026-09-29T21:02:05+00:00</updated>
<author>
<name>Arthur Hanson Rasmusson</name>
<email>arthur@vgpu.io</email>
</author>
<published>2026-09-29T21:02:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.vgpu.io/open-iov.git/commit/?id=d37825435946a47e1f9b66aee8764aba5362b138'/>
<id>urn:sha1:d37825435946a47e1f9b66aee8764aba5362b138</id>
<content type='text'>
The failing wait is uvm_tracker_wait_for_entry inside channel_pool_add
(UVM_GPU_REGISTER): capture the tracker entry's channel pointer and value so
the host can tell which release value is still missing.
</content>
</entry>
<entry>
<title>kernel: authoritative host-injected VA-&gt;PA pins (ipin table) + wider pin table</title>
<updated>2026-09-29T17:52:49+00:00</updated>
<author>
<name>Arthur Hanson Rasmusson</name>
<email>arthur@vgpu.io</email>
</author>
<published>2026-09-29T17:52:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.vgpu.io/open-iov.git/commit/?id=d6dde0ecac4f031ea27a27df7767cba54ac44f55'/>
<id>urn:sha1:d6dde0ecac4f031ea27a27df7767cba54ac44f55</id>
<content type='text'>
The CE push-buffer page 0x120000000 resolved to a zero-filled page even after
sema_map_add injected the correct translation: the shared pin table silently
dropped inserts once a hash cluster exceeded the 32-probe window (the page
hashes to slot 0, a hot cluster), and lookups fell through to the
content-scanned map and answered with a stale page - so every CE push read as
implausible and memset stayed 0. Injected translations now live in a separate
authoritative table checked before every other source and are never written by
self-discovery; the general pin table is 4x larger with a 4x probe window and
counts drops (pin_drop/ipin_drop) in the stats line. guest_kprobes.sh disables
the kprobe group before removal (EBUSY) and matches p:kprobes/&lt;name&gt;; the
guest wait sampler can run counters-only with GDB=0.
</content>
</entry>
<entry>
<title>guest-diag: deterministic channel-&gt;pool-&gt;manager-&gt;pushbuffer chain + chunk-read diagnostics</title>
<updated>2026-09-29T17:32:46+00:00</updated>
<author>
<name>Arthur Hanson Rasmusson</name>
<email>arthur@vgpu.io</email>
</author>
<published>2026-09-29T17:32:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.vgpu.io/open-iov.git/commit/?id=058076bc81249864bd70615f30e73c95ccfd9bc1'/>
<id>urn:sha1:058076bc81249864bd70615f30e73c95ccfd9bc1</id>
<content type='text'>
semfix_watch.py now resolves the CE pushbuffer from guest truth instead of
scanning a wide raw window: it walks uvm_channel_t +0=pool, pool+0=manager,
manager+8=pushbuffer, pushbuffer+8=rm_mem, rm_mem+0x10=vas[] and prefers the
rm_mem whose GPU VA is in the 0x120000000 CE pushbuffer range. Three entry
points: uvch probe on __uvm_push_begin_acquire_on_channel_with_info, uvbp
probe on uvm_pushbuffer_begin_push, and the uvmt tracking-sem kptr (channel
scan back from sem). Misses now print structured hop counters so a failed
chunk read is distinguishable from a failed chain. guest_kprobes.sh
(re)installs uvmt/uvch/uvbp/uvpbf after every guest boot (plain, module:
and bare spellings).
</content>
</entry>
</feed>
