linux-stable.git/arch/s390/kernel/syscalls.S, branch linux-3.7.y

s390/syscalls: wire up kcmp system call

2012-09-26T13:45:17+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

s390: add support for runtime instrumentation

2012-09-26T13:45:02+00:00

Allow user-space threads to use runtime instrumentation (RI). To enable RI
for a thread there is a new s390 specific system call, sys_s390_runtime_instr,
that takes as parameter a realtime signal number. If the RI facility is
available the system call sets up a control block for the calling thread with
the appropriate permissions for the thread to modify the control block.

The user-space thread can then use the store and modify RI instructions to
alter the control block and start/stop the instrumentation via RION/RIOFF.

If the user specified program buffer runs full RI triggers an external
interrupt. The external interrupt is translated to a real-time signal that
is delivered to the thread that enabled RI on that CPU. The number of
the real-time signal is the number specified in the RI system call. So,
user-space can select any available real-time signal number in case the
application itself uses real-time signals for other purposes.

The kernel saves the RI control blocks on task switch only if the running
thread was enabled for RI. Therefore, the performance impact on task switch
should be negligible if RI is not used.

RI is only enabled for user-space mode and is disabled for the supervisor
state.

Reviewed-by: Heiko Carstens 
Signed-off-by: Jan Glauber 
Signed-off-by: Martin Schwidefsky

[S390] wire up process_vm syscalls

2011-11-14T10:19:08+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

All Arch: remove linkage for sys_nfsservctl system call

2011-08-26T22:09:58+00:00

The nfsservctl system call is now gone, so we should remove all
linkage for it.

Signed-off-by: NeilBrown 
Signed-off-by: J. Bruce Fields 
Signed-off-by: Linus Torvalds

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

[S390] wire up sys_syncfs

2011-03-23T09:15:58+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

[S390] wire up sys_clock_adjtime

2011-03-23T09:15:58+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

[S390] wire up sys_open_by_handle_at

2011-03-23T09:15:58+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

[S390] wire up sys_name_to_handle_at

2011-03-23T09:15:58+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky

[S390] wire up prlimit64 and fanotify* syscalls

2010-08-13T08:06:54+00:00

Signed-off-by: Heiko Carstens 
Signed-off-by: Martin Schwidefsky