Add explicit bounded ARM diagnostic trace tiers - #2
Merged
Merged
Conversation
NiSeullent
added a commit
that referenced
this pull request
Sep 14, 2026
Add explicit bounded ARM diagnostic trace tiers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a separate explicit diagnostic parser for bounded 256/1024/4096 instruction tiers. The existing API keeps its 64-instruction platform-profile and 8-instruction no-profile limits. Larger ceilings never provision missing platform state, bypass configuration validation, or permit arbitrary budgets.
A fresh standalone clone passes all Core tests and the no-default-features build. Configuration tests cover tier/ceiling combinations, default compatibility, invalid values and unchanged handoff/memory/platform checks. An isolated opt-in EFI build also executed exactly 256 authored instructions while the ordinary EFI rejected that budget before entry; firmware wiring and receipts are integrated separately. This is bounded diagnostics, not normal macOS startup.