Repository navigation
Validate Stax on Intel Linux after enabling perf permissions - #54
Merged
Merged
Conversation
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
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.
The Intel Linux pilot previously stopped at perf_event_open permission denial. After the operator enabled perf access, live Redis capture, native archive replay, and the optional CLI/SQLite/registered MCP workflow passed on the Core Ultra 7 155U host.
Update the pilot report, machine-readable evidence, and plan/usage links with the completed checks. Preserve the original failed attempt, pinned builds, artifact hashes, all twelve performance trials, and measurement limitations. No production code changes.
Three baseline/profiled pairs at each of 900 Hz and 99 Hz do not establish the 5% overhead budget: baseline max/min throughput varied by 26% and 38%, respectively. All six profiled trials reported zero lost events and DWARF truncations. Wakeup attribution remains unavailable, kernel addresses are unresolved, and nonzero P-core PMU fields do not establish per-process CPI/TMA.
Validation on base f6b4e7e:
Raw archives/logs remain local under ~/.cache/topdown-stax-linux-pilot; hashes and summaries are committed. Apple CPU validation and controlled-host overhead acceptance remain separate work.