diff options
author | 2018-08-11 01:04:55 +0100 | |
---|---|---|
committer | 2018-08-16 21:02:17 -0400 | |
commit | 060581c158a66fcc68f8877ccd0d60fd9aeca65e (patch) | |
tree | 93b2c4f9b849dbf6a3f0751569154755307019ce /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Merge tag 'for-linus-4.19-ofs1' of git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux (diff) | |
download | linux-dev-060581c158a66fcc68f8877ccd0d60fd9aeca65e.tar.xz linux-dev-060581c158a66fcc68f8877ccd0d60fd9aeca65e.zip |
alpha: use alpha_ni_syscall only for syscall zero
Once upon a time it used to have a C part that printed a warning
about unimplemented OSF syscalls. That's what it's been doing
all over the OSF syscall range, while the native Linux syscall
range uses sys_ni_syscall().
With those warnings about unimplemented OSF syscalls gone (circa 2.4),
alpha_ni_syscall() has shrunk to that little bit of asm and the
only reason it hasn't been replaced with sys_ni_syscall() everywhere
is that extra twist needed in case of syscall #0.
Let's keep it only for syscall #0 and replace the rest with sys_ni_syscall.
And use sys_ni_syscall for "number out range" in ptraced-call case, as
we'd been doing for normal codepath since 2.1.86...
Acked-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions