zloop: ensure zsys_init() when creating zloop #2286
Merged
Conversation
This file contains 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
If no sockets or actors are used in zloop, `zsys_init()` does not get run and zsys interrupt handler does not get initialized. This means that interrupts will not work correctly in zloop if, for example, only timers are used. `zsys_init()` is safe to call multiple times, so we ensure that it's called when new zloop instance is created.
|
thnx! |
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.
If no sockets or actors are used in zloop,
zsys_init()does not get run and zsys interrupt handler does not get initialized. This means that interrupts will not work correctly in zloop if, for example, only timers are used.zsys_init()is safe to call multiple times, so we ensure that it's called when new zloop instance is created.