diff options
| author | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-01 00:04:25 -0400 |
|---|---|---|
| committer | Arthur Hanson Rasmusson <arthur@vgpu.io> | 2026-10-01 00:04:25 -0400 |
| commit | 9459bc5a98821dec22bf6ed908829245ae4bc026 (patch) | |
| tree | b1df01d81cd0146514a43bbfa35ffdcb7caea9f6 /kernel/gsp_phys_gpu.c | |
| parent | 11947e2bf97945e68d9deff9018cdb46d81438ba (diff) | |
| download | open-iov-9459bc5a98821dec22bf6ed908829245ae4bc026.tar.gz open-iov-9459bc5a98821dec22bf6ed908829245ae4bc026.zip | |
docs: record the board power-domain hazard and D0-lock mitigation for the physical backend
- New 4.2: describe behaviourally how the option-D claim path can
power-gate the board on driver release (platform power resource behind
the root port, off/on sequence via the embedded controller), the two
observed host freezes (no crash record), and the D0 lock now applied
across release -> claim -> rebind: runtime-PM forbid + D3cold disable on
the GPU, its board companion functions and the root port, config-space
verification while claimed and again before rebind, abort with the locks
held on any power-loss signature, runtime-PM restore after the
distribution driver's probe.
- 4.1/4.3: the lock is a required ownership step; returning to the normal
driver is conditional, not assumed; real GSP boot not started.
- 2/3(A): fresh no-unbind evidence - no exported RM/vGPU symbols and no
manager daemon in the stock distribution build.
- 6: driver-API baseline re-verified 64/64; ownership + firmware staging
verified; power-domain lock implemented pending supervised verification.
- 7/8: residual out-of-band power-cut risk, supervised-test requirement,
and the gsp_phys_gpu + gsp_phys_hazard_ack operating constraint.
Diffstat (limited to 'kernel/gsp_phys_gpu.c')
0 files changed, 0 insertions, 0 deletions