-
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
[entropy_src] Backpressure handling follow-up work #21855
Labels
Component:Doc
Documentation issue
Component:DV
DV issue: testbench, test case, etc.
Earlgrey-PROD Candidate
Temporary label to triage issues into Earlgrey-PROD Milestones
IP:entropy_src
Subsystem:Entropy
entropy_src, csrng, or edn related issues
Milestone
Comments
vogelpi
added
Component:Doc
Documentation issue
Component:DV
DV issue: testbench, test case, etc.
Subsystem:Entropy
entropy_src, csrng, or edn related issues
IP:entropy_src
labels
Mar 6, 2024
vogelpi
added
the
Earlgrey-PROD Candidate
Temporary label to triage issues into Earlgrey-PROD Milestones
label
Mar 6, 2024
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Mar 28, 2024
This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Mar 29, 2024
This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Mar 29, 2024
This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
This was referenced Mar 29, 2024
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Mar 29, 2024
This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Mar 29, 2024
This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
that referenced
this issue
Mar 29, 2024
This is related to #21855. Signed-off-by: Pirmin Vogel <[email protected]>
We should do this for M5. Discussed with @h-filali that this one of the next things to investigate after coverage closure. IIRC, I've only noted test failures due to backpressure in the rng_max_rate test. |
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Jul 1, 2024
When running in Firmware Override: Observe mode, this bit should be checked. If it's asserted, this means that health tested entropy bits have been dropped before the postht FIFO due to conditioner back pressure. This means entropy observed via observe FIFO may be non-contiguous. This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Jul 1, 2024
When running in Firmware Override: Observe mode, this bit should be checked. If it's asserted, this means that health tested entropy bits have been dropped before the postht FIFO due to conditioner back pressure. This means entropy observed via observe FIFO may be non-contiguous. This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Jul 1, 2024
If any of the postht, distr or precon FIFOs are non-empty when triggering the conditioner, there is risk of leaving entropy bits tested as part of the current window inside the pipeline instead of absorbing them into the current seed. This would be problematic. This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
that referenced
this issue
Jul 2, 2024
When running in Firmware Override: Observe mode, this bit should be checked. If it's asserted, this means that health tested entropy bits have been dropped before the postht FIFO due to conditioner back pressure. This means entropy observed via observe FIFO may be non-contiguous. This is related to #21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
to vogelpi/opentitan
that referenced
this issue
Jul 2, 2024
If any of the postht, distr or precon FIFOs are non-empty when triggering the conditioner, there is risk of leaving entropy bits tested as part of the current window inside the pipeline instead of absorbing them into the current seed. This would be problematic. This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
vogelpi
added a commit
that referenced
this issue
Jul 2, 2024
If any of the postht, distr or precon FIFOs are non-empty when triggering the conditioner, there is risk of leaving entropy bits tested as part of the current window inside the pipeline instead of absorbing them into the current seed. This would be problematic. This is related to #21855. Signed-off-by: Pirmin Vogel <[email protected]>
AlexJones0
pushed a commit
to AlexJones0/opentitan
that referenced
this issue
Jul 8, 2024
When running in Firmware Override: Observe mode, this bit should be checked. If it's asserted, this means that health tested entropy bits have been dropped before the postht FIFO due to conditioner back pressure. This means entropy observed via observe FIFO may be non-contiguous. This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
AlexJones0
pushed a commit
to AlexJones0/opentitan
that referenced
this issue
Jul 8, 2024
If any of the postht, distr or precon FIFOs are non-empty when triggering the conditioner, there is risk of leaving entropy bits tested as part of the current window inside the pipeline instead of absorbing them into the current seed. This would be problematic. This is related to lowRISC#21855. Signed-off-by: Pirmin Vogel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Component:Doc
Documentation issue
Component:DV
DV issue: testbench, test case, etc.
Earlgrey-PROD Candidate
Temporary label to triage issues into Earlgrey-PROD Milestones
IP:entropy_src
Subsystem:Entropy
entropy_src, csrng, or edn related issues
Description
What is left from #21799 for after M2:
The text was updated successfully, but these errors were encountered: