Add event system #3
Closed
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
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.
This is WIP to add a simple event system to the analyzer stream.
The way it works is to have a special case for the packet length field. Any length from
0xFF00upwards is an event, with the low byte being an event code. This is followed by a 16-bit timestamp but no packet data.Thus, we get 256 event codes we can use, and all events are timestamped.
To handle timestamp wrapping, we define a
NONEevent which is emitted when the timestamp is0xFFFFand no packet has started. This ensures the timestamp of the next packet is not ambiguous.