diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-18 16:01:43 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-18 16:01:58 -0400 |
| commit | 077879fa5ca410d387bdc913fae12effcc47799b (patch) | |
| tree | 649067a81e3a05f582635447c1ccb76b0848d27f /wiki/open-iov.org/images/thumb/4/43/VFIO_Diagram.png | |
| parent | 436e66f51242071ef57205a40b1aee20cba3539a (diff) | |
| download | open-iov-master.tar.gz open-iov-master.zip | |
r235: only 4 of the probe's ~9 64KB copies reached the ring (the
sema_bigcopy_log budget had absorbed the rest - the A H2D is missing
entirely), and the events lack direction/buffer identity. Now:
- every total==65536 copy bypasses the bigcopy budget (its own 128-line
A-TRACE budget still bounds volume) so the probe's H2D and all D2H
readbacks always appear;
- A-TRACE carries dir=H2D/D2H (device=VID low-pa, host=SYS high-pa) plus
pt=P1/P2 (upload read/landed) or P4/P4R (readback source/result).
r235 decode so far: the A upload lands ([0 1 2 3] in device pa 0x7800000
at t=.94) and the SAME device page is later rewritten to
[16382 16383 8193 8194] - h_A's own values at shifted offsets - with the
pattern repeated across consecutive device pages (0x7800000/0x7810000/
0x7820000), i.e. a repeated-page/offset-wrapped write inside the emulated
copy or engine path, not client-side. The trace fix makes the next capture
name the exact path (missing H2D included).
(cherry picked from commit 9b35145136c949405c7fb4d22b3405c174ecb055)
Diffstat (limited to 'wiki/open-iov.org/images/thumb/4/43/VFIO_Diagram.png')
0 files changed, 0 insertions, 0 deletions
