From: Pete Zaitcev <zaitcev@redhat.com>
To: schwidefsky@de.ibm.com
Cc: linux-arch@vger.kernel.org, zaitcev@redhat.com, akpm@osdl.org,
jakub@redhat.com
Subject: FUTEX_CMP_REQUEUE and 6-argument syscall
Date: Thu, 3 Jun 2004 11:02:21 -0700 [thread overview]
Message-ID: <20040603110221.1fe58b53.zaitcev@redhat.com> (raw)
Hi, Martin,
the following changeset adds an extra argument for sys_futex:
http://linux.bkbits.net:8080/linux-2.5/gnupatch@40bca55f9uSk3jznb3RD7ltnQvJKbA
So, now we have a syscall with 6 arguments. Do you have any suggestions
how to handle it on s390? The main decision would be if we stick to
the C calling convention and put a pointer to the list into %r7, or
if we just put the argument into %r7 (thus precluding syscalls with
7 arguments for sure, but saving a get_user somewhere). After that
we need to change arch/s390/kernel/entry.S:trace_svc, and the 31 bit
compat wrapper.
I'm curious if any other architecture was caught out by this.
-- Pete
next reply other threads:[~2004-06-03 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 18:02 Pete Zaitcev [this message]
2004-06-03 18:13 ` FUTEX_CMP_REQUEUE and 6-argument syscall Ralf Baechle
2004-06-03 21:26 ` David S. Miller
2004-06-03 23:27 ` Pete Zaitcev
2004-06-04 0:33 ` Paul Mackerras
2004-06-04 7:44 ` Russell King
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=20040603110221.1fe58b53.zaitcev@redhat.com \
--to=zaitcev@redhat.com \
--cc=akpm@osdl.org \
--cc=jakub@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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