-
Notifications
You must be signed in to change notification settings - Fork 781
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
[edn] Investigate why there are many EDN requests after ROM_EXT #22819
Comments
Together with @pamaury, I've been able to track down the issue: keymgr has an internal, SW-configurable timer to automatically reseed it's local PRNG. The current ROM_EXT implementation doesn't alter the default value of 0x100, meaning keymgr is constantly reseeding it's internal PRNG every 256 clock cycles. What's really problematic about this is that the counter doesn't currently factor in whether the PRNG is actually advanced or not. This is problematic as it leads to several issues:
For now, ROM_EXT should probably be changed to configure the max reseeding interval of 65536 clock cycles. This will still request a reseed operation every 655us which is not going to be sufficient, but it might already help against some of the issues we have seen on different fronts. FYI @moidx @timothytrippel I am filing another issue start discussing design changes for keymgr, because we really should change this and there are easy changes we can do. |
Update: the following changes have been made to alleviate/fix the underlying issue:
I am thus closing this issue now. |
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see #22819 (comment) This is related to #21706 and #22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see #22819 (comment) This is related to #21706 and #22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
Description
When working on the
edn_kat
test, I have identified a strange behaviour that only seems to happen when running the ROM_EXT: there seems to be too many requests going through the EDN. Specifically, we stop the entropy complex, setup the EDN in auto mode and start gathering 10 words of entropy thought the Ibex. By the time the Ibex has gotten 10 words, CSRNG reports that it got 150 requests through EDN0 (each generate commands generates 16 words).Investigate why this number is so high.
Ping @vogelpi @h-filali
The text was updated successfully, but these errors were encountered: