kernel: Fix GSP emulation shadow binding, eventfd wiring, RPC livelocks + docs suite + repo reorg

CRITICAL FIXES (guest driver bring-up):
- gsp_emulation.c: emulation engine bound to the WRONG BAR0 - it polled the
  host physical BAR0 (bars[0].vaddr ioremap) for the doorbell and read RPCs
  from a local dma_alloc_wc buffer, while the guest writes land in the
  vzalloc'd bar0_shadow. The RPC path could never work; PBA writes even
  corrupted the host GPU's physical BAR0+0x3000. gsp_emu_init now binds
  exclusively to bar0_shadow (doorbell/mailbox/PBA aliases;
  shared_mem_dma==0 marks the alias so cleanup never dma_free's it).
- main.c SET_IRQS: DATA_EVENTFD eventfds were DISCARDED ('TODO' + kfree) -
  the guest never received MSI-X completions. Full wiring now:
  eventfd_ctx_fdget per vector, fd -1 clears, dev_close releases refs.
  gsp_emu_inject_completion_interrupt looks up vgpu->irqs[0].trigger LIVE
  (init-time copy was permanently NULL since QEMU wires after gsp_emu_init).
- gsp_rpc_client.c: BAR_TRAP/MIGRATE in emulation mode called
  gsp_rpc_submit_raw which rings the SAME doorbell the thread polls -
  self-triggered RPC livelock + multi-second stalls. Now fail fast with
  -ENOTSUPP + pr_warn_ratelimited (guest BAR access is direct MMIO).

MORE FIXES:
- main.c: nv_vgpu_config_write returned SIZE_MAX (while(count--) wrap) and
  was dead code while the VFIO write handler did unfiltered byte copies
  (guest could rewrite vendor ID/BARs). Return fixed; VFIO write handler
  now routes through the per-register filter.
- kernel/Makefile: M=$(PWD) used the env var which is stale when invoked
  via the top-level make (pointed at repo root -> kbuild silently built
  NOTHING; explains every 'stale .ko' incident). Now M=$(CURDIR).
- Warnings sweep: header prototypes for mdev/type functions, format casts
  in gsp_comm.c DRY-RUN logs, unused variable.

ROBUSTNESS (harness/tooling):
- vgpu_vm.py: run had no timeout (start could block forever);
  guest_shell recv could block forever on a wedged guest. Both now bounded;
  guest_shell pre-flights guest-ping and reports wedge diagnostics.
- stack_manager.sh: qemu/qemu-debug now launch via the vgpu_vm.py harness
  (workflow rule: never raw QEMU).

REPO REORGANIZATION:
- driver/ (legacy guest-side gsp-vgpu.ko) moved to legacy-driver-guest/
  (reference only, not built; README explains). 3 legacy un-buildable test
  files moved to legacy-driver-guest/kernel-tests/. Top-level Makefile
  cleaned of the dead DRIVER_DIR reference.

DOCUMENTATION SUITE (new):
- docs/GSP_EMULATION_ARCHITECTURE.md - emulator deep-dive: shadow BAR0
  model, doorbell protocol, dispatch table, MSI-X path, lifecycle, memory-
  model caveats
- docs/DEBUGGING.md - QEMU GDB stub workflow, serial console, QMP NMI,
  failure taxonomy, full bring-up validation checklist, EPT-livelock case
  study, version-matrix discipline
- docs/ONBOARDING.md - repo tour, coding standards (incl. virt_to_phys /
  dma_addr_t / get-put rules), first build & test
- docs/VERSION_UPGRADE.md - end-to-end new-driver-version procedure
  (firmware fetch, Ghidra analysis, configs, signatures, validation)
- docs/PERFORMANCE.md - bare-metal A/B methodology + targets
- README.md doc index; STATE.md refreshed; DEVELOPMENT_WORKFLOW.md corrected
  (load order: open-iov-vfio BEFORE nvidia; stock-driver blacklist note)

1 files changed, 22 insertions, 8 deletions

diff --git a/scripts/stack_manager.sh b/scripts/stack_manager.sh
index 0b62170..ef8385a 100755
--- a/scripts/stack_manager.sh
+++ b/scripts/stack_manager.sh
@@ -11,6 +11,8 @@ FIRMWARE_PATH="$BASE_DIR/firmware/57X-GSP/570.144/gsp-570.144.fwimage.bin"
 FIRMWARE_DEST="/lib/firmware/gsp-570.144.fwimage.bin"
 
 MDEV_SCRIPT="$BASE_DIR/scripts/create_mdev.sh"
+# Legacy direct-QEMU script retained for reference only - VM launch MUST go
+# through the harness (vgpu_vm.py). See cmd_launch_qemu.
 QEMU_SCRIPT="$BASE_DIR/scripts/launch_qemu_vgpu.sh"
 TEST_SCRIPT="$BASE_DIR/scripts/test_vgpu_stack.sh"
 
@@ -226,12 +228,16 @@ cmd_list_mdev() {
 # ============================================================
 
 cmd_launch_qemu() {
-    log_info "Launching QEMU with vGPU..."
-    if [[ ! -f "$QEMU_SCRIPT" ]]; then
-        log_err "launch_qemu_vgpu.sh not found"
+    # WORKFLOW RULE: always use the QEMU harness (vgpu_vm.py), never 
+    # or raw QEMU directly - the harness owns , mdev lifecycle, QMP,
+    # guest-agent and serial logging.
+    local harness="$BASE_DIR/scripts/vgpu_vm.py"
+    if [[ ! -f "$harness" ]]; then
+        log_err "vgpu_vm.py harness not found at $harness"
         return 1
     fi
-    "$QEMU_SCRIPT" "$@"
+    log_info "Launching QEMU with vGPU via harness (vgpu_vm.py)..."
+    "$harness" start "${1:-vgpu-linux}"
 }
 
 # ============================================================
@@ -273,12 +279,20 @@ cmd_dmesg() {
 }
 
 cmd_debug_qemu() {
-    log_info "Starting debug QEMU session..."
-    if [[ ! -f "$BASE_DIR/scripts/debug_guest_init.sh" ]]; then
-        log_err "debug_guest_init.sh not found"
+    # WORKFLOW RULE: harness only. The vgpu-linux.yaml already sets
+    # serialLog=/tmp/vgpu-guest-serial.log and gdbPort=1234, so a normal
+    # harness start IS the debug session: attach GDB with
+    #   gdb -ex 'target remote localhost:1234'
+    # and follow the guest serial log plus host dmesg.
+    local harness="$BASE_DIR/scripts/vgpu_vm.py"
+    if [[ ! -f "$harness" ]]; then
+        log_err "vgpu_vm.py harness not found at $harness"
         return 1
     fi
-    "$BASE_DIR/scripts/debug_guest_init.sh" "$@"
+    log_info "Starting debug session via harness (GDB stub tcp::1234, serial /tmp/vgpu-guest-serial.log)..."
+    "$harness" start "${1:-vgpu-linux}"
+    log_info "Attach GDB: gdb -ex 'target remote localhost:1234'"
+    log_info "Serial log: tail -f /tmp/vgpu-guest-serial.log"
 }
 
 cmd_cleanup_crash() {