linux-toradex.git/arch/sh/kernel/syscalls_32.S, branch v3.0.2

ns: Wire up the setns system call

2011-05-28T17:48:39+00:00

32bit and 64bit on x86 are tested and working.  The rest I have looked
at closely and I can't find any problems.

setns is an easy system call to wire up.  It just takes two ints so I
don't expect any weird architecture porting problems.

While doing this I have noticed that we have some architectures that are
very slow to get new system calls.  cris seems to be the slowest where
the last system calls wired up were preadv and pwritev.  avr32 is weird
in that recvmmsg was wired up but never declared in unistd.h.  frv is
behind with perf_event_open being the last syscall wired up.  On h8300
the last system call wired up was epoll_wait.  On m32r the last system
call wired up was fallocate.  mn10300 has recvmmsg as the last system
call wired up.  The rest seem to at least have syncfs wired up which was
new in the 2.6.39.

v2: Most of the architecture support added by Daniel Lezcano 
v3: ported to v2.6.36-rc4 by: Eric W. Biederman 
v4: Moved wiring up of the system call to another patch
v5: ported to v2.6.39-rc6
v6: rebased onto parisc-next and net-next to avoid syscall  conflicts.
v7: ported to Linus's latest post 2.6.39 tree.

>  arch/blackfin/include/asm/unistd.h     |    3 ++-
>  arch/blackfin/mach-common/entry.S      |    1 +
Acked-by: Mike Frysinger 

Oh - ia64 wiring looks good.
Acked-by: Tony Luck 

Signed-off-by: Eric W. Biederman 
Signed-off-by: Linus Torvalds

sh: wire up sys_sendmmsg.

2011-05-23T05:41:32+00:00

Signed-off-by: Paul Mundt

sh: wire up sys_syncfs.

2011-03-22T12:56:08+00:00

Signed-off-by: Paul Mundt

sh: Wire up new fhandle and clock_adjtime syscalls.

2011-03-17T08:01:24+00:00

Signed-off-by: Paul Mundt

sh: wire up accept4 syscall (non-multiplexed path)

2010-12-14T08:58:10+00:00

Signed-off-by: Carmelo Amoroso 
Signed-off-by: Paul Mundt

sh: Provide a non-multiplexed sys_recvmmsg path.

2010-09-14T08:43:11+00:00

Now that the rest of the socket calls are provided through their own
paths, do the same for sys_recvmmsg. It's unlikely we'll ever be able to
kill off the socketcall path, but this at least permits userspace to
gradually begin migrating.

Signed-off-by: Paul Mundt

sh: Add syscall entries for non multiplexed socket calls

2010-09-14T08:37:53+00:00

Linux kernel already has socket syscalls that can be invoked
without the multiplexing sys_socketcall wrapper.
C library wrappers are ready to use them directly. It needs just
to define the missing syscall numbers and provide the related entries
into the syscalls table, like sh64 aleady does.

Signed-off-by: Francesco Rundo 
Signed-off-by: Carmelo Amoroso 
Signed-off-by: Paul Mundt

sh: wire up fanotify/prlimit64 syscalls.

2010-08-16T04:51:18+00:00

Signed-off-by: Paul Mundt

sh: unwire sys_recvmmsg.

2010-01-19T08:00:06+00:00

sh32 at the moment only uses sys_socketcall to reach these, so unwire
recvmmsg for now. While we're at it, add it to the ignore list, as per
the s390 change.

Signed-off-by: Paul Mundt

sh: Wire up recvmmsg syscall.

2009-12-11T06:29:31+00:00

The stub already existed in the _64 syscall table, but was lacking a
__NR_recvmmsg definition, while it was absent entirely for _32 variants.

Signed-off-by: Paul Mundt