Introduce Warm-up Phase for Dudect Measurement #289
+14
−2
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.
This pull request introduces a warm-up phase to the function that collects and processes measurement batches in qtest.c, skipping the first batch to reduce timing variance in queue operations, such as insert_tail. Inspired by Reparaz et al.’s 2016 paper, "Dude, is my code constant time?", this change adapts the leakage detection approach from the dudect prototype. Unlike the author’s implementation , which uses dynamic percentile checks, this approach employs a static boolean to mark the initial run, better suiting the fixed test loop. Experiments in simulation mode with insert_tail, using perf, show a minor 1.5% reduction in standard deviation (from 449ms to 442ms), suggesting a small improvement in execution stability.