OpenDevicePartnership / OpenDevicePartnership/odp-platform-common
Run matched-policy randomized C BDS vs patina_boot A/B
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 5
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 9
Description
Parent: #190
Goal
Bound implementation cost after removing boot-policy differences from the comparison.
Scope
- define a common minimal policy contract for both arms
- emit identical phase markers for dispatch, connection, EndOfDxe, ReadyToBoot, LoadImage, StartImage, and ExitBootServices
- run at least 10 randomized/interleaved warm boots per arm and an agreed cold-boot sample
- report distribution, confidence interval, p50/p95, outliers, and phase attribution
Acceptance criteria
- parity checklist passes before measurement begins
- image order is randomized and provenance is captured
- raw FPDT and logger evidence is published
- presentation claims are updated from the resulting statistical bound
Related: #108 #119 #121 #124 #183
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading parent issue #190 and related issues #108, #119, #121, #124, and #183 to establish the matched-policy contract and parity checklist. Then define how both arms emit the listed phase markers and how randomized warm boots, cold boots, FPDT data, logger evidence, and provenance will be collected; done means the statistical report and presentation claims reflect the resulting bound.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- operating-systems, performance, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100