[aes] Upstream support for GCM - Part 21 #29275
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
Accidentally, trigger[3] was used for the PTX as well as for the TAG measurements, causing trigger overlaps. This commit uses trigger[4] for the TAG measurement, as it should be. Signed-off-by: Pascal Nasahl <[email protected]>
vogelpi
requested review from
andrea-caforio,
moidx and
nasahlpa
and removed request for
a team and
moidx
nasahlpa
approved these changes
Feb 6, 2026
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.
This is the 21st PR of a series of PRs to upstream support for AES-GCM. The original PR can be found here: vogelpi#29
[aes,sca] Fix AES-GCM PTX measurement
Accidentally, trigger[3] was used for the PTX as well as for the TAG measurements, causing trigger overlaps. This commit uses trigger[4] for the TAG measurement, as it should be.