-
Notifications
You must be signed in to change notification settings - Fork 2
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
Clarify PSW address reported for signal handlers #2
Comments
Thanks. Yes, I agree this should be documented, and that the existing ABI section about the exception interface is the right place for it. |
More information about exceptions has been added with commit b53ce24, including the value of the PSW address after a fault. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On s390x, SIGILL, SIGFPE, and SIGTRAP 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.
This behavior effectively forms part of the kernel ABI. Given that the ABI already has a section 1.5 Exception Interface that documents the relationship between architecture exceptions and kernel signals, we should add the information about where the reported PSW points to depending on the signal type to that chapter as well.
The text was updated successfully, but these errors were encountered: