Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[multitop] port aes_smoketest to multitop #26242

Merged
merged 2 commits into from
Feb 11, 2025

Conversation

nbdd0121
Copy link
Contributor

@nbdd0121 nbdd0121 commented Feb 11, 2025

Fix #26208
Fix #26209
Fix #26210

@nbdd0121 nbdd0121 requested a review from pamaury February 11, 2025 12:03
@nbdd0121 nbdd0121 requested a review from a team as a code owner February 11, 2025 12:03
Copy link
Contributor

@pamaury pamaury left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Just a quick comment: technically the name kDtAes is a top-specific because each top can name instances the way it wants to. Therefore if a top wanted to name is AES instance 'myaes' then the test would not compile. It's also unclear how to deal with tops with several AES blocks (if that ever happens). Therefore the "right" thing to do would probably be this:

// Pick the first AES block.
dt_aes_t kAesUnderTest = (dt_aes_t)0;
static_assert(kDtAesCount >= 1, "This test requires at least one AES instance");

This test does not actually use entropy_testutils, so remove the
dependency and it's a simple port.

Signed-off-by: Gary Guo <[email protected]>
@nbdd0121
Copy link
Contributor Author

I think I prefer to keep using kDtAes for now

@nbdd0121 nbdd0121 merged commit 69222ee into lowRISC:master Feb 11, 2025
42 checks passed
@nbdd0121 nbdd0121 deleted the aes-multitop branch February 11, 2025 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants