Project Status - Revision history

WikiBot: Fix repository links: point to the cgit tree URLs

2026-10-12T04:41:00Z

Fix repository links: point to the cgit tree URLs

← Older revision		Revision as of 04:41, 12 October 2026
Line 3:		Line 3:
	= Project Status =		= Project Status =

	<blockquote>'''What this page is.''' The honest, dated state of the project: what works today, what is in progress, and what is not started. It is refreshed periodically and each claim maps to a maintained document in the repository. Canonical sources: [https://git.vgpu.io/open-iov/~~blob/master~~/docs/README.md <code>../docs/README.md</code>] (project front door), [https://git.vgpu.io/open-iov/~~blob/master~~/docs/04-implementation/01-known-knowns-and-unknowns.md <code>../docs/04-implementation/01-known-knowns-and-unknowns.md</code>] (known-knowns and known-unknowns) and [https://git.vgpu.io/open-iov/~~blob/master~~/docs/04-implementation/03-execution-frontier.md <code>../docs/04-implementation/03-execution-frontier.md</code>] (the execution frontier). When this page and the docs disagree, the docs tree wins.</blockquote>		<blockquote>'''What this page is.''' The honest, dated state of the project: what works today, what is in progress, and what is not started. It is refreshed periodically and each claim maps to a maintained document in the repository. Canonical sources: [https://git.vgpu.io/open-iov.git/tree/docs/README.md <code>../docs/README.md</code>] (project front door), [https://git.vgpu.io/open-iov.git/tree/docs/04-implementation/01-known-knowns-and-unknowns.md <code>../docs/04-implementation/01-known-knowns-and-unknowns.md</code>] (known-knowns and known-unknowns) and [https://git.vgpu.io/open-iov.git/tree/docs/04-implementation/03-execution-frontier.md <code>../docs/04-implementation/03-execution-frontier.md</code>] (the execution frontier). When this page and the docs disagree, the docs tree wins.</blockquote>

	Status: 2026-10-12, tree <code>master @ 2f066727</code>. Tags: <code>[live]</code> proven with the stock guest driver; <code>[gated]</code> implemented, default-off or behind supervised gates; <code>[wip]</code> partially implemented; <code>[wall]</code> current blocker; <code>[target]</code> named success state; <code>[planned]</code> designed, not built.		Status: 2026-10-12, tree <code>master @ 2f066727</code>. Tags: <code>[live]</code> proven with the stock guest driver; <code>[gated]</code> implemented, default-off or behind supervised gates; <code>[wip]</code> partially implemented; <code>[wall]</code> current blocker; <code>[target]</code> named success state; <code>[planned]</code> designed, not built.
Line 56:		Line 56:
	== 2. What "CUDA works" means here ==		== 2. What "CUDA works" means here ==

	A green <code>nvidia-smi</code> or even a passing driver-API smoke is not "CUDA works". The project's definition of done for CUDA requires all of the following ([https://git.vgpu.io/open-iov/~~blob/master~~/docs/04-implementation/01-known-knowns-and-unknowns.md <code>../docs/04-implementation/01-known-knowns-and-unknowns.md</code>]):		A green <code>nvidia-smi</code> or even a passing driver-API smoke is not "CUDA works". The project's definition of done for CUDA requires all of the following ([https://git.vgpu.io/open-iov.git/tree/docs/04-implementation/01-known-knowns-and-unknowns.md <code>../docs/04-implementation/01-known-knowns-and-unknowns.md</code>]):

	# Stock guest driver probe, <code>nvidia-smi</code>, device enumeration — done.		# Stock guest driver probe, <code>nvidia-smi</code>, device enumeration — done.

WikiBot: Carry the site-wide About/licensing message on every page (2026-10-12)

2026-10-12T04:29:51Z

Carry the site-wide About/licensing message on every page (2026-10-12)

← Older revision		Revision as of 04:29, 12 October 2026
Line 1:		Line 1:
			{{About message}}

	= Project Status =		= Project Status =

WikiBot: Add page from tracked wiki source (2026 IA update)

2026-10-12T04:22:14Z

Add page from tracked wiki source (2026 IA update)

New page

= Project Status =

<blockquote>'''What this page is.''' The honest, dated state of the project: what works today, what is in progress, and what is not started. It is refreshed periodically and each claim maps to a maintained document in the repository. Canonical sources: [https://git.vgpu.io/open-iov/blob/master/docs/README.md <code>../docs/README.md</code>] (project front door), [https://git.vgpu.io/open-iov/blob/master/docs/04-implementation/01-known-knowns-and-unknowns.md <code>../docs/04-implementation/01-known-knowns-and-unknowns.md</code>] (known-knowns and known-unknowns) and [https://git.vgpu.io/open-iov/blob/master/docs/04-implementation/03-execution-frontier.md <code>../docs/04-implementation/03-execution-frontier.md</code>] (the execution frontier). When this page and the docs disagree, the docs tree wins.</blockquote>

Status: 2026-10-12, tree <code>master @ 2f066727</code>. Tags: <code>[live]</code> proven with the stock guest driver; <code>[gated]</code> implemented, default-off or behind supervised gates; <code>[wip]</code> partially implemented; <code>[wall]</code> current blocker; <code>[target]</code> named success state; <code>[planned]</code> designed, not built.

== 1. Milestone ladder ==

{| class="wikitable"
|-
! Milestone
! State
|-
| Emulated vGPU device (PCI, BARs, MSI-X, VFIO mdev)
| <code>[live]</code> working
|-
| GSP boot emulation (FWSEC / booter / RISCV handshake)
| <code>[live]</code> working
|-
| GSP-RM message queues and RPC transport
| <code>[live]</code> working
|-
| Stock guest driver probe and <code>nvidia-smi</code> (TU104)
| <code>[live]</code> working
|-
| CUDA userspace init and the driver-API smoke (<code>cuInit</code>, device enumeration, <code>cuCtxCreate</code>, allocation, copies, free, destroy)
| <code>[live]</code> working — the smoke prints <code>ALL OK</code> and the 64-byte payload round-trips exactly
|-
| Guest CUDA kernel execution on real hardware
| <code>[wall]</code> a forwarded guest launch reaches the engine queue (the front end deposits the methods and the scheduling path accepts them), but the engine does not yet execute the forwarded launch descriptor — an engine-authored release has not been observed. Emulation-mode kernel runs (executed through the host bridge on a no-claim path) have completed green; reproducibility of the green path across boots is an open issue
|-
| Physical backend on real hardware (module-owned GPU running its real GSP-RM)
| <code>[live]</code> boot, RPC session, object creation and copy-engine work proven; GR execution is the same frontier as above
|-
| Multi-tenant isolation (mdev per VM, per-context page directories)
| <code>[wip]</code> designed; the baseline service-state ownership work is in progress
|-
| OpenGL / Vulkan (3D), video
| <code>[planned]</code>
|-
| Windows guests
| <code>[planned]</code> (target)
|-
| Xen / Argo / OpenXT / Qubes Air transports
| <code>[planned]</code> (the emulation core is hypervisor-independent by construction)
|-
| Live migration
| <code>[planned]</code>
|-
| Performance numbers
| <code>[planned]</code> — no published numbers yet; any claim will ship with its measurement methodology
|}

== 2. What "CUDA works" means here ==

A green <code>nvidia-smi</code> or even a passing driver-API smoke is not "CUDA works". The project's definition of done for CUDA requires all of the following ([https://git.vgpu.io/open-iov/blob/master/docs/04-implementation/01-known-knowns-and-unknowns.md <code>../docs/04-implementation/01-known-knowns-and-unknowns.md</code>]):

# Stock guest driver probe, <code>nvidia-smi</code>, device enumeration — done.
# Context creation and the full driver-API surface (<code>cuMemAlloc</code>, copies, free, destroy) — done.
# A guest kernel launch that '''executes on real hardware''' and is proven by an engine-authored completion — the current frontier.
# Memory the guest's work refers to resolving correctly end to end (the VA↔PA model) — partially, for the paths exercised so far.
# Correct completion, semaphore and fault semantics back to the guest — CE class work has the relay; GR is open.
# Reproducibility: every boot, not a lucky one — an open issue.
# No ad-hoc default-off parameters required for the canonical path.

Until every gate holds, the honest formulation is: '''initialization and the driver-API path work; engine execution is in progress.'''

== 3. How to see it yourself ==

The reference setup takes about half an hour from a fresh host ([[Install and First Run|<code>Install-and-First-Run.md</code>]]); the current expected outcome is exactly the ladder above — driver probe, <code>nvidia-smi</code>, the full driver-API smoke, and the execution frontier where it stands. The risc-v-gsp-rm-debugger workbench ([[risc-v-gsp-rm-debugger|<code>Riscv-GSP-RM-Debugger.md</code>]]) is the host-side tooling used to study the firmware side of that frontier.

== 4. How this page is maintained ==

Every claim above carries a date and a tag, maps to a maintained document in the repository, and is refreshed as milestones land. The execution story, with its evidence and its open theories, is on [[The Execution Frontier|<code>Execution-Frontier.md</code>]].

== 5. Related pages ==

* [[Install and First Run|<code>Install-and-First-Run.md</code>]]
* [[System Overview|<code>System-Overview.md</code>]]
* [[The Execution Frontier|<code>Execution-Frontier.md</code>]]
* [[Hardware and Software Matrix|<code>Hardware-Software-Matrix.md</code>]] — which hardware and software combinations are Reference, Target or Experimental.
* [[FAQ|<code>FAQ.md</code>]]