Require explicit selection for a bounded deeper ARM trace - #6
Merged
Merged
Conversation
NiSeullent
added a commit
that referenced
this pull request
Sep 14, 2026
Require explicit selection for a bounded deeper ARM trace
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 parser entry requiring the exact deep-16384 selector,16384 budget and named software platform profile. Existing default64/8 and extended256/1024/4096 APIs retain their limits and reject the deep-only selector. The firmware SHA-256 correction is retained.
A fresh standalone clone passes260 all-target tests, no-default and doctests, and actual debug/release UEFI code generation. Authored EFI evidence separately verifies exact16384 retirement/fetch counts, existing lower tiers, ordinary-firmware rejection and a real4096-clamped negative. Original diagnostics remain incomplete-SPTM observations; this capability does not establish normal macOS boot.