[not-matthias]

As discussed, to avoid timing differences keep the instruction feature flag enabled.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The change affects amd64 feature reporting for guests using deterministic RNG.

The PR appears safe to merge, with a non-blocking request to retain the CPUID test checks.

Findings

1.  CPUID checks are gone ▶

Fix with agent prompt

### Issue 1
none/tests/amd64/deterministic_rng.c:38
The test no longer checks the behavior this revert restores. Keep the CPUID queries and change the expected bits to `1`: `deterministic_rng.vgtest` already requires both features before running. Without those checks, hiding either feature again would leave this test passing.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Restores host-based CPUID flags for RDRAND and RDSEED when deterministic RNG is enabled.

• Deterministic RNG keeps host-supported RDRAND and RDSEED visible in CPUID.

_{Reviews (1) · Last reviewed commit: "Revert "feat(vex): hide RDRAND and RDSEE..." · Reviewed by Greptile}

[greptile-apps]

CPUID checks are gone

The test no longer checks the behavior this revert restores. Keep the CPUID queries and change the expected bits to 1: deterministic_rng.vgtest already requires both features before running. Without those checks, hiding either feature again would leave this test passing.

Prompt To Fix With AI

This is a comment left during a code review.
Path: none/tests/amd64/deterministic_rng.c
Line: 38

Comment:
**CPUID checks are gone**

The test no longer checks the behavior this revert restores. Keep the CPUID queries and change the expected bits to `1`: `deterministic_rng.vgtest` already requires both features before running. Without those checks, hiding either feature again would leave this test passing.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[codspeed]

Merging this PR will not alter performance

✅ 84 untouched benchmarks
⏩ 60 skipped benchmarks¹

---

_{Comparing cod-3957-determinstic-rng-2 (817bee1) with master (81d7365)}

Footnotes

1. 60 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩