From: Robert Love <rml@novell.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: akpm@osdl.org, paulus@samba.org, linux-kernel@vger.kernel.org,
ttb@tentacle.dhs.org
Subject: Re: [patch] inotify: ppc64 syscalls.
Date: Wed, 27 Jul 2005 16:31:02 -0400 [thread overview]
Message-ID: <1122496262.21253.190.camel@betsy> (raw)
In-Reply-To: <20050727.132701.115907512.davem@davemloft.net>
On Wed, 2005-07-27 at 13:27 -0700, David S. Miller wrote:
> You'll notice that sys_ppc32.c has a ton of shims which purely
> exist to sign extend "int" system call arguments. Sparc64 does
> something similarly, but in assembler so that we don't eat the
> overhead of a full stack frame just to sign extend arguments.
Yah, but it looked like they did the sign extend thing for every int but
file descriptors, and fd's are the only int's we have.
Robert Love
next prev parent reply other threads:[~2005-07-27 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 15:45 [patch] inotify: ppc32 syscalls Robert Love
2005-07-27 16:55 ` Andrew Morton
2005-07-27 17:31 ` [patch] inotify: ppc64 syscalls Robert Love
2005-07-27 20:27 ` David S. Miller
2005-07-27 20:31 ` Robert Love [this message]
2005-07-27 20:33 ` David S. Miller
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=1122496262.21253.190.camel@betsy \
--to=rml@novell.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ttb@tentacle.dhs.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