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 sig
From: Robert Love <[EMAIL PROTECTED]>
Date: Wed, 27 Jul 2005 16:31:02 -0400
> 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,
From: Robert Love <[EMAIL PROTECTED]>
Date: Wed, 27 Jul 2005 13:31:36 -0400
> [ I don't think we need sys32 compatibility versions--and if we do, I
> failed in life. ]
add_watch and rm_watch both do, because system call arguments are
zero-extended by default for compat tasks, thus the "fd" arg ne
On Wed, 2005-07-27 at 09:55 -0700, Andrew Morton wrote:
> ppc64 likes to keep its 32-bit-syscall table in sync with ppc32 so it'd be
> best to do ppc64 while we're at it (both sys_call_table and
> sys_call_table32)
Sure thing.
Attached find inotify system call support for PPC64.
[ I don't think
4 matches
Mail list logo