summaryrefslogtreecommitdiffstats
path: root/config/hardware/turing.yaml
diff options
context:
space:
mode:
authorOpen-IOV <dev@open-iov.org>2026-09-23 05:44:08 -0400
committerOpen-IOV <dev@open-iov.org>2026-09-23 05:46:43 -0400
commit68cdd7728a7cc6715bbbff7decfe2b11c3bdf558 (patch)
tree3dc8ce2e6af313a97ec6852f5c663a9a93665d2e /config/hardware/turing.yaml
downloadopen-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 'config/hardware/turing.yaml')
-rw-r--r--config/hardware/turing.yaml70
1 files changed, 70 insertions, 0 deletions
diff --git a/config/hardware/turing.yaml b/config/hardware/turing.yaml
new file mode 100644
index 0000000..1257ba3
--- /dev/null
+++ b/config/hardware/turing.yaml
@@ -0,0 +1,70 @@
+# Turing Architecture Configuration (TU102, TU104, TU106)
+architecture:
+ name: "turing"
+ description: "NVIDIA Turing architecture (RTX 20-series, T4, Quadro RTX)"
+ pci_vendor_id: 0x10DE
+ pci_device_ids:
+ - 0x1E82 # TU102
+ - 0x1E83
+ - 0x1E84
+ - 0x1E85
+ - 0x1E86
+ - 0x1E87
+ - 0x1E88
+ - 0x1E89
+ - 0x1E8A
+ - 0x1E8B
+ - 0x1E8C
+ - 0x1E8D
+ - 0x1E8E
+ - 0x1E8F
+ - 0x1ED0 # TU104
+ - 0x1ED1
+ - 0x1ED2
+ - 0x1ED3
+ - 0x1ED4
+ - 0x1ED5
+ - 0x1ED6
+ - 0x1ED7
+ - 0x1ED8
+ - 0x1ED9
+ - 0x1EDA
+ - 0x1EDB
+ - 0x1EDC
+ - 0x1EDD
+ - 0x1EDE
+ - 0x1EDF
+ bar_layout:
+ bar0:
+ size_mb: 16
+ type: "config"
+ description: "Control registers, doorbell, shared memory"
+ bar1:
+ size_mb: 256
+ type: "vram"
+ description: "VRAM aperture"
+ bar2:
+ size_mb: 32
+ type: "reserved"
+ description: "Reserved"
+ bar3:
+ size_mb: 32
+ type: "reserved"
+ description: "Reserved"
+ gsp:
+ doorbell_offset: 0x110C00
+ shared_mem_offset: 0x1000
+ shared_mem_size_kb: 4
+ firmware_version: "570.144W"
+ msix:
+ table_offset: 0x2000
+ pba_offset: 0x3000
+ vectors: 32
+ limits:
+ max_vfs: 8
+ vram_size_gb: 16
+ page_size_kb: 4
+ features:
+ mig: false
+ sriov: true
+ vgpu: true \ No newline at end of file