i#6884: Add drmemtrace signal number marker #6885
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
Adds a new drmemtrace marker holding the signal number which is
emitted after the kernel event marker. It is not emitted at the
signal return point; only at the transfer to the handler.
Does not add a feature bit or increase the version as this marker is
considered optional and so no mechanism is provided for users to be
guaranteed that it is present.
Adds view tool support.
Adds a test that the marker is emitted in the burst_gencode test.
Output from the test's trace:
```
52 32: 1616564 ifetch 2 byte(s) @ 0x00007f615935d023 0f 0b ud2
53 32: 1616564 <marker: kernel xfer from 0x7f615935d023 to handler>
54 32: 1616564 <marker: signal #4>
55 32: 1616564 <marker: timestamp 13365562571171519>
56 32: 1616564 <marker: tid 1616564 on core 9>
57 33: 1616564 ifetch 1 byte(s) @ 0x00005641b091170b 55 push %rbp
```
Fixes #6884
abhinav92003
approved these changes
Jul 16, 2024
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.
Adds a new drmemtrace marker holding the signal number which is emitted after the kernel event marker. It is not emitted at the signal return point; only at the transfer to the handler.
Does not add a feature bit or increase the version as this marker is considered optional and so no mechanism is provided for users to be guaranteed that it is present.
Adds view tool support.
Adds a test that the marker is emitted in the burst_gencode test. Output from the test's trace:
Fixes #6884