You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For tso/non-tso memory tracking, we might be able to group accesses between atomic ops in transactions, and detect concurrent access with transaction aborts. Might get us more precise tracking than the MTE approach.
For synchronous detection of segfaults, we might be able to wrap code between guest abi sync points around a transaction, and on transaction abort execute some slowpath. Details on synchronous signal complications in #1682
This discussion was converted from issue #1732 on August 10, 2022 17:19.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Following up from yesterday's discussion,
For
tso
/non-tso
memory tracking, we might be able to group accesses between atomic ops in transactions, and detect concurrent access with transaction aborts. Might get us more precise tracking than the MTE approach.For synchronous detection of segfaults, we might be able to wrap code between guest abi sync points around a transaction, and on transaction abort execute some slowpath. Details on synchronous signal complications in #1682
TME Extension details: https://developer.arm.com/documentation/101028/0012/16--Transactional-Memory-Extension--TME--intrinsics?lang=en
Beta Was this translation helpful? Give feedback.
All reactions