Bump FireMarshal for linux rng init fix#1620
Merged
Conversation
abejgonzalez
approved these changes
Oct 11, 2023
jerryz123
approved these changes
Oct 11, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue: In the absence of a hardware random number generator, applications are blocked on
dev/urandomwhile the system gains entropy. Gaining entropy unnecessarily consumes lots of sim cycles and applications appear to silently hang.This PR adds Kconfig options to firesim/linux and uses them in FireMarshal to artificially set entropy during early boot.
Related PRs / Issues:
firesim/FireMarshal: rng init fix: update firesim/linux submodule + update linux-config to use Kconfig options #289firesim/linux: Initialize random number generator in early boot #4Type of change:
Impact:
Contributor Checklist:
mainas the base branch?changelog:<topic>label?changelog:label?.conda-lock.ymlfile if you updated the conda requirements file?Please Backport?