generated from erix/meta
[FEATURE] Describe fixed PCI assignments in the original platform handover #14
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-handoff#14
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
Native DeviceFrame loans need the original device-resource backing. Configuration access, BAR coordinates and firmware resource descriptions cannot supply that owner.
Proposed behavior and scope
Capture actual firmware-assigned root-bridge, function and BAR resources while UEFI protocols remain live. Transfer the retained assignment ledger through the original successful platform takeover. Add a known BootKernel 2.4 extension with bounded root/function/window/BAR tables and original device-path data; retain the exact standard configuration header once per function.
Logical UEFI BAR numbers remain distinct from configuration dword slots. Preserve both CPU and PCI spans, raw translations and the specific provider convention. The initial mode keeps fixed assignments; relocation and DMA isolation are separate work.
Authority, security and reliability
The source is the actual one-shot platform takeover, scoped by original assigned allocations and real parent occupations. Safe decoding creates only descriptions. A bridge aperture is routing scope, not a child allocation grant. Parent identity must agree with original firmware association and actual bridge routing; ambiguous ancestry does not broaden scope.
Exclude RAM, runtime images, boot sources, stacks, tables, APIC and independent firmware/device occupations. Framebuffer overlap needs a genuine same-origin relationship. Retain owners through failure and uncertain cleanup; after an attempted firmware exit, unrecoverable failure must not return to firmware. Every directly exposed page requires authority for all of its bytes.
Acceptance criteria
Alternatives and tradeoffs
Inferring ownership from BAR reads or memory-kind labels would bypass the original source. UEFI section 7 supplies the actual platform-management transition; PCI descriptions delimit existing assignments. The precise UEFI provider’s translation definition must be preserved rather than inferred from generic ACPI semantics. Unknown firmware ancestry or translation remains closed until supported explicitly.
Tracking and rollout
Coordinates Kernel #145. Builds on the loaded-runtime-image handover and its partial-exit custody. The codec, actual producer and original native consumer must be introduced together before opening DeviceFrame construction.
Primary contracts: UEFI boot services and UEFI PCI support.