diff options
| author | Open-IOV <dev@open-iov.org> | 2026-09-23 05:44:08 -0400 |
|---|---|---|
| committer | Open-IOV <dev@open-iov.org> | 2026-09-23 05:46:43 -0400 |
| commit | 68cdd7728a7cc6715bbbff7decfe2b11c3bdf558 (patch) | |
| tree | 3dc8ce2e6af313a97ec6852f5c663a9a93665d2e /tools/guest-diag/push_guest_tools.sh | |
| download | open-iov-68cdd7728a7cc6715bbbff7decfe2b11c3bdf558.tar.gz open-iov-68cdd7728a7cc6715bbbff7decfe2b11c3bdf558.zip | |
Open-IOV: initial public release
Open-IOV virtualizes NVIDIA GPUs so that unmodified guest drivers run with
real GPU functionality - CUDA first, 3D and video to follow - on unmodified
hosts, without a proprietary vGPU license and without patching any driver,
firmware or hypervisor.
Core principle: emulate the interface, pass through the work.
kernel/ open-iov-vfio.ko - host VFIO mdev driver: virtual GPU device
(PCI config space, BAR shadows, MSI-X), GSP boot emulation,
GSP-RM message-queue/RPC emulation, memory model (GPU-VA to
guest-PA discovery) and the semaphore-completion service that
advances guest UVM progress.
userspace/ libiov.so management API and examples.
tools/ guest diagnostics, firmware analysis wrappers, RM probes.
scripts/ stack manager, VM harness, build/load/test automation.
config/ hardware/version profiles (the portability surface).
docs/ documentation tree - start at docs/README.md.
wiki/ long-form firmware and protocol deep dives.
Status: initialization works end to end for a stock 570.144 Linux guest on
Turing (TU104): driver probe, nvidia-smi, the full GSP-RM control battery,
object creation and the early CUDA/UVM start-up path. GPU work forwarding -
the step that makes CUDA kernels execute on real hardware - is the active
work item; see docs/04-implementation/01-known-knowns-and-unknowns.md.
License: BSD-3-Clause for the project; GPL-2.0 for kernel modules that link
GPL-only kernel interfaces. See LICENSE and docs/09-reference/legal-and-licensing.md.
Diffstat (limited to 'tools/guest-diag/push_guest_tools.sh')
| -rwxr-xr-x | tools/guest-diag/push_guest_tools.sh | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/tools/guest-diag/push_guest_tools.sh b/tools/guest-diag/push_guest_tools.sh new file mode 100755 index 0000000..a2a3dbb --- /dev/null +++ b/tools/guest-diag/push_guest_tools.sh @@ -0,0 +1,31 @@ +#!/bin/bash +# push_guest_tools.sh - (re)build the guest-side diagnostic binaries from the +# sources kept in this directory. The guest's /tmp is wiped on boot, so run +# this after every VM start; the sources here are the persistent copies. +# +# Usage: tools/guest-diag/push_guest_tools.sh +# (env: VM="vgpu-linux" is not needed; scripts/vgpu_vm.py talks to the +# running VM's guest agent socket) +set -e + +HERE="$(cd "$(dirname "$0")" && pwd)" +VMEXEC="$HERE/../../scripts/vgpu_vm.py" +REPO="$HERE/../.." + +push_b64() { # push_b64 <local file> <remote file> + local b64 + b64=$(base64 -w0 "$1") + "$VMEXEC" exec "echo '$b64' | base64 -d > '$2'" >/dev/null 2>&1 +} + +echo "[*] pushing sources..." +push_b64 "$HERE/ptrace_ioctl.c" /tmp/ptio.c +push_b64 "$HERE/guest_engines.c" /tmp/ge.c +push_b64 "$HERE/rmq_probe.c" /tmp/rmqp.c +push_b64 "$REPO/tools/test/cuda_drv_test.c" /tmp/cdt.c + +echo "[*] compiling in guest..." +"$VMEXEC" exec "gcc -O1 -w -o /tmp/ptio /tmp/ptio.c && \ +gcc -O1 -w -o /tmp/ge /tmp/ge.c && \ +gcc -O1 -w -o /tmp/rmqp /tmp/rmqp.c && \ +gcc -O1 -o /tmp/cdt /tmp/cdt.c -ldl && echo BUILD_OK" |
