linux-user: Drop direct use of openat etc syscalls
authorPeter Maydell <peter.maydell@linaro.org>
Wed, 12 Jun 2013 15:20:21 +0000 (16:20 +0100)
committerPeter Maydell <peter.maydell@linaro.org>
Wed, 12 Jun 2013 15:20:21 +0000 (16:20 +0100)
commitc0d472b12e8c5ba81c69b28a1088ff52a59933f2
tree8c1dce6c8da8f82c3d8cba31aa6dd5057d0e3f1f
parent3307e2363a812e4f68d02ec3b0114a9b510702b7
linux-user: Drop direct use of openat etc syscalls

The linux-user syscall emulation layer currently supports the
openat family of syscalls via two mechanisms: simply calling
the corresponding libc functions, and making direct syscalls.
Since glibc has supported these functions since at least glibc
2.5, there's no real need to retain the (essentially untested)
direct syscall fallback code, so simply delete it. This allows
us to remove some ifdeffery that was attempting to disable
provision of some of the syscalls if the host didn't seem to
support them, which in some cases was actually wrong (eg where
there are several flavours of the syscall and we only need
one of them, not necessarily the exact one the guest has,
as with the fstatat* calls).

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <rth@twiddle.net>
Tested-by: Claudio Fontana <claudio.fontana@huawei.com>
Message-id: 1370126121-22975-2-git-send-email-peter.maydell@linaro.org
linux-user/syscall.c