From: Sven Schnelle <svens@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Michal Suchánek" <msuchanek@suse.de>,
"Peter Zijlstra" <peterz@infradead.org>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RFC 0/2] s390: keep syscall number / return value in separate pt_regs members
Date: Wed, 15 Jul 2026 15:38:28 +0200 [thread overview]
Message-ID: <20260715133830.2619853-1-svens@linux.ibm.com> (raw)
After a recent discussion on the ML about syscall semantics wrt. pre-initializing
the return value to -ENOSYS and the special handling s390 has, I made two patches to
clean that up. See the commit messages for more details.
The second patch is just a cleanup and could be dropped if not wanted.
Sven Schnelle (2):
s390/syscall: Keep syscall return in extra ptregs member
s390/syscall: Keep syscall number in extra ptregs member
arch/s390/include/asm/ptrace.h | 9 ++++++---
arch/s390/include/asm/syscall.h | 13 +++++++------
arch/s390/kernel/ptrace.c | 2 +-
arch/s390/kernel/signal.c | 12 +++++-------
arch/s390/kernel/syscall.c | 26 +++++++-------------------
5 files changed, 26 insertions(+), 36 deletions(-)
--
2.53.0
next reply other threads:[~2026-07-15 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 13:38 Sven Schnelle [this message]
2026-07-15 13:38 ` [PATCH 1/2] s390/syscall: Keep syscall return in extra ptregs member Sven Schnelle
2026-07-15 13:38 ` [PATCH 2/2] s390/syscall: Keep syscall number " Sven Schnelle
2026-07-15 13:59 ` Heiko Carstens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260715133830.2619853-1-svens@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=msuchanek@suse.de \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome