DynamoRIO / DynamoRIO/dynamorio
scheduler not udpating direct switch block start time, resulting in too-short blocks
Open
Component-DrMemtrace
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 629
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 30
Description
In testing my per-core-runqueue https://github.com/DynamoRIO/dynamorio/issues/6938 implementation I noticed that the drmemtrace scheduler was not setting the block start time for direct switches, meaning that they didn't block long enough as they compared to whatever the prior start value was.
Contributor guide
Assessment
This issue has not been assessed yet.