From: "David S. Miller" <davem@redhat.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: zaitcev@redhat.com, schwidefsky@de.ibm.com,
linux-arch@vger.kernel.org, akpm@osdl.org, jakub@redhat.com
Subject: Re: FUTEX_CMP_REQUEUE and 6-argument syscall
Date: Thu, 3 Jun 2004 14:26:30 -0700 [thread overview]
Message-ID: <20040603142630.6004d38f.davem@redhat.com> (raw)
In-Reply-To: <20040603181345.GA26083@linux-mips.org>
On Thu, 3 Jun 2004 20:13:45 +0200
Ralf Baechle <ralf@linux-mips.org> wrote:
> > I'm curious if any other architecture was caught out by this.
>
> 6 is the limit on o32 MIPS where we pass 4 arguments in registers and two
> on the stack but it would be easy to extend that. On 64-bit kernels we
> only use upto 8 register arguments but no stack arguments ever so I hope
> we don't exceed that limit ever ...
6 is the limit on Sparc/Sparc64 as well, registers %o0 - %o5 carry
arguments.
next prev parent reply other threads:[~2004-06-03 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 18:02 FUTEX_CMP_REQUEUE and 6-argument syscall Pete Zaitcev
2004-06-03 18:13 ` Ralf Baechle
2004-06-03 21:26 ` David S. Miller [this message]
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=20040603142630.6004d38f.davem@redhat.com \
--to=davem@redhat.com \
--cc=akpm@osdl.org \
--cc=jakub@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=zaitcev@redhat.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