Trap handler changes to support s390x#2871
Merged
Merged
Conversation
On s390x, SIGILL and SIGFPE are delivered with the PSW address pointing *after* the faulting instruction, while SIGSEGV and SIGBUS are delivered with the PSW address pointing *to* the faulting instruction. In order to support this, the common code trap handler has to distinguish between those cases. Also, enable SIGFPE on s390x (just like on x86).
uweigand
force-pushed
the
s390x-traphandler
branch
from
97978b2 to
d7402d8
Compare
alexcrichton
approved these changes
May 3, 2021
| // signals on the first byte of the instruction (as usual). This | ||
| // means we simply need to decrement the reported PSW address by | ||
| // one in the case of a "late" signal here to ensure we always | ||
| // correctly find the associated trap handler. |
Member
There was a problem hiding this comment.
Is there an online link to gist here which goes into some more detail? I'm mostly just curious for my own edification!
Member
Author
There was a problem hiding this comment.
That's a good question. Right now, I don't think this is documented anywhere but by reading the Linux kernel sources. This should probably be added to the ABI document. I've added an issue there as a reminder: IBM/s390x-abi#2
Member
There was a problem hiding this comment.
Ok, sounds reasonable to me!
mchesser
pushed a commit
to mchesser/wasmtime
that referenced
this pull request
May 24, 2021
On s390x, SIGILL and SIGFPE are delivered with the PSW address pointing *after* the faulting instruction, while SIGSEGV and SIGBUS are delivered with the PSW address pointing *to* the faulting instruction. In order to support this, the common code trap handler has to distinguish between those cases. Also, enable SIGFPE on s390x (just like on x86).
This file contains hidden or 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
2 participants
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.
On s390x, SIGILL and SIGFPE are delivered with the PSW address
pointing after the faulting instruction, while SIGSEGV and
SIGBUS are delivered with the PSW address pointing to the
faulting instruction. In order to support this, the common
code trap handler has to distinguish between those cases.
Also, enable SIGFPE on s390x (just like on x86).