From: Christoph Hellwig <hch@lst.de>
To: linuxppc-dev@ozlabs.org
Subject: sign extension for 32bit syscalls on ppc64
Date: Fri, 28 Apr 2006 15:12:54 +0200 [thread overview]
Message-ID: <20060428131254.GA507@lst.de> (raw)
For 32bit syscalls implemented in arch/powerpc/ we're doing our own
sign-extension where an int argument is passed as u32 in the prototype
and then casted to int later on:
asmlinkage long compat_sys_sendfile(u32 out_fd, u32 in_fd, compat_off_t
__user * offset, u32 count)
{
...
ret = sys_sendfile((int)out_fd, (int)in_fd, up, count);
..
}
OTOH various syscalls in the generic code don't do that and it seems to
still work fine. I have patches for various new generic compat
routines, and they all seem to work fine without this sign extension.
What's the exact sign extention rules for ppc64?
next reply other threads:[~2006-04-28 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 13:12 Christoph Hellwig [this message]
2006-04-28 23:32 ` sign extension for 32bit syscalls on ppc64 Paul Mackerras
2006-04-29 1:30 ` Stephen Rothwell
2006-04-29 2:33 ` Paul Mackerras
2006-04-29 3:16 ` Stephen Rothwell
2006-04-29 3:42 ` Stephen Rothwell
2006-04-29 13:46 ` Andreas Schwab
2006-05-01 0:05 ` Stephen Rothwell
2006-05-01 3:44 ` Stephen Rothwell
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=20060428131254.GA507@lst.de \
--to=hch@lst.de \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).