kernel: execute pushed CE work (PTE memsets, copies) and track semaphores

The progress service now decodes push buffers as method streams and performs
the work the driver pushes, not just the tracking semaphore:

- C5B5 method decoder: SET_REMAP_CONST_A/B + COMPONENTS + OFFSET_OUT +
  LINE_LENGTH_IN + LAUNCH_DMA = memset (into vidmem or guest RAM);
  OFFSET_IN + OFFSET_OUT + LAUNCH_DMA = copy; SET_SEMAPHORE_A/B/PAYLOAD +
  LAUNCH_DMA = release. Contiguous method runs (count 2/4) are applied in
  full - OFFSET_IN/OUT arrive as one run.
- Pushes span page boundaries, so pages are decoded as method streams
  without a start marker. Collected operations execute only when the
  push's release is reached and still pending (payload ahead of the
  semaphore), so recycled buffers replaying old pushes are skipped and
  their stale memsets cannot overwrite newer state.
- VA->PA map is first-wins: stale copies of freed allocations and
  unrelated adjacent u64 pairs produced bogus entries that hijacked a
  good mapping and sent semaphore writes to the wrong page.
- dump_guest module parameter (hex dump of guest PA, kthread via
  completion; kthread_stop before the thread runs loses the work).

With this the guest no longer stalls in uvm_tracker_wait and no longer
oopses in the UVM path; the failure moved to a userspace segfault inside
libcuda (NULL-0x38) after the driver's page allocations.

Also add tools/cuda-ab: run one deterministic CUDA workload on the host
(bare metal oracle) and in the guest, then compare the stable result
lines. The binary links the CUDA runtime statically so the guest only
needs the driver's libcuda.so.

0 files changed, 0 insertions, 0 deletions