Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i#2350 rseq: Translate from rseq region to handler #3757

Merged
merged 1 commit into from
Jul 26, 2019

Conversation

derekbruening
Copy link
Contributor

On any translation, and in particular on detach, we translate from
inside an rseq region to the abort handler. This is necessary to
avoid problems with a cpu migration earlier in the region while
running the instrumented version.

Augments the api.rseq test with a thread that sits in a loop in an
rseq region to test translation on detach: without the translation, it
loops forever.

Issue: #2350

On any translation, and in particular on detach, we translate from
inside an rseq region to the abort handler.  This is necessary to
avoid problems with a cpu migration earlier in the region while
running the instrumented version.

Augments the api.rseq test with a thread that sits in a loop in an
rseq region to test translation on detach: without the translation, it
loops forever.

Issue: #2350
@derekbruening derekbruening merged commit ec729f0 into master Jul 26, 2019
@derekbruening derekbruening deleted the i2350-rseq-detach branch July 26, 2019 19:38
hgreving2304 pushed a commit that referenced this pull request Jul 31, 2019
On any translation, and in particular on detach, we translate from
inside an rseq region to the abort handler.  This is necessary to
avoid problems with a cpu migration earlier in the region while
running the instrumented version.

Augments the api.rseq test with a thread that sits in a loop in an
rseq region to test translation on detach: without the translation, it
loops forever.

Issue: #2350
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants