Reference
This chapter is the single source of truth for schemas, parameters, versions, file paths, the GART format and known issues. Other chapters explain behaviour and link here so that no table is maintained twice.
Recommended reading paths
First guest boot or a driver that does not load: read Guest parameters, then look up the symptom in Known issues.
Writing or changing a topology YAML: look up fields and defaults in Topology YAML schema, device launch contracts in Device adapters, and the end-to-end walkthrough in Writing topologies.
Reproducing a build or checking version drift: start from Version matrix, then locate artifacts, logs and sources with Files and artifacts.
Adding or reviewing a vHost image recipe: see vHost image recipes for fields and artifacts, then Add a vHost image recipe for the workflow.
Debugging GPU address translation and GART tables: GART format has the entry and register formats; the translation flow is in GPU address translation.
Maintaining or comparing the legacy shell launcher: Legacy launcher flags is the only option table for that path.
Canonical ownership
Page |
Owned content |
Primary source |
|---|---|---|
Topology and vHost fields, types, defaults and limits |
|
|
Adapter parameters, argv and readiness probes |
|
|
vHost image recipe directories, fields, input identity and bundle format |
|
|
amdgpu module parameters, ROM write, kernel cmdline, IP block mask |
|
|
Recorded versions, image tags and provenance |
|
|
Source directories, build outputs, session directories, guest files and environment variables |
Repository layout, |
|
GART PTEs, aperture registers and typical layout |
|
|
Issue catalog organized by symptom, cause and fix |
Historical issue records, driver and model behaviour |
|
Corrected shell-launcher and gem5-config option tables |
|