1. 04 Jun, 2015 1 commit
    • Ingo Molnar's avatar
      x86/asm/entry: Move the arch/x86/syscalls/ definitions to arch/x86/entry/syscalls/ · 1f57d5d8
      Ingo Molnar authored
      The build time generated syscall definitions are entry code related, move
      them into the arch/x86/entry/ directory.
      
      Cc: Borislav Petkov <bp@alien8.de>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Andy Lutomirski <luto@amacapital.net>
      Cc: Denys Vlasenko <dvlasenk@redhat.com>
      Cc: Brian Gerst <brgerst@gmail.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: linux-kernel@vger.kernel.org
      Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
      1f57d5d8
  2. 20 May, 2014 1 commit
  3. 25 Sep, 2012 1 commit
  4. 17 Nov, 2011 1 commit
  5. 20 Dec, 2010 1 commit
  6. 25 Jun, 2010 1 commit
    • Chris Metcalf's avatar
      Add wait4() back to the set of <asm-generic/unistd.h> syscalls. · b51cae21
      Chris Metcalf authored
      The initial pass at the generic ABI assumed that wait4() could be
      easily expressed using waitid().  Although it's true that wait4()
      can be built on waitid(), it's awkward enough that it makes more
      sense to continue to include wait4 in the generic syscall ABI.
      
      Since there is already a deprecated wait4 in the ABI, this change
      converts that wait4 into old_wait, and puts wait4 in the next
      available slot for new supported syscalls, after the platform-specific
      syscalls at number 260.
      Signed-off-by: default avatarChris Metcalf <cmetcalf@tilera.com>
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      b51cae21
  7. 11 Jun, 2009 1 commit
    • Arnd Bergmann's avatar
      asm-generic: add a generic unistd.h · e64a1617
      Arnd Bergmann authored
      A new architecture should only define a minimal set of system
      calls while still providing the full functionality. This version
      of unistd.h has gone through intensive review to make sure that
      by default it only enables syscalls that do not already have
      a more featureful replacement.
      
      It is modeled after the x86-64 version of unistd.h, which unifies
      the syscall number definition and the actual system call table
      in a single file, in order to keep them synchronized much more
      easily.
      
      This first version still keeps legacy system call definitions
      around, guarded by various #ifdefs, and with numbers larger
      than 1024. The idea behind this is to make it easier for
      new architectures to transition from a full list to the reduced
      set. In particular, the new microblaze architecture that should
      migrate to using the generic ABI headers can at least use an
      existing uClibc source tree without major rewrites during the
      conversion.
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      e64a1617
  8. 29 Oct, 2008 1 commit
  9. 23 Oct, 2008 1 commit
  10. 11 Oct, 2007 1 commit
  11. 28 Jun, 2007 1 commit
    • David Woodhouse's avatar
      Introduce fixed sys_sync_file_range2() syscall, implement on PowerPC and ARM · edd5cd4a
      David Woodhouse authored
      Not all the world is an i386.  Many architectures need 64-bit arguments to be
      aligned in suitable pairs of registers, and the original
      sys_sync_file_range(int, loff_t, loff_t, int) was therefore wasting an
      argument register for padding after the first integer.  Since we don't
      normally have more than 6 arguments for system calls, that left no room for
      the final argument on some architectures.
      
      Fix this by introducing sys_sync_file_range2(int, int, loff_t, loff_t) which
      all fits nicely.  In fact, ARM already had that, but called it
      sys_arm_sync_file_range.  Move it to fs/sync.c and rename it, then implement
      the needed compatibility routine.  And stop the missing syscall check from
      bitching about the absence of sys_sync_file_range() if we've implemented
      sys_sync_file_range2() instead.
      
      Tested on PPC32 and with 32-bit and 64-bit userspace on PPC64.
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      Acked-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Paul Mackerras <paulus@samba.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      edd5cd4a
  12. 02 May, 2007 1 commit
    • Sam Ravnborg's avatar
      kbuild: complain about missing system calls · c53aeca0
      Sam Ravnborg authored
      Most system calls seems to get added to i386 first. This patch
      automatically generates a warning for any new system call which is
      implemented on i386 but not the architecture currently being compiled.
      On PowerPC at the moment, for example, it results in these warnings:
      init/missing_syscalls.h:935:3: warning: #warning syscall sync_file_range not implemented
      init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented
      init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented
      
      The file scripts/checksyscalls.sh list a number of legacy system calls
      that are ignored because they only makes sense on i386 systems.
      
      Other contributors to this patch are Russell King <rmk+lkml@arm.linux.org.uk>
      and Stéphane Jourdois <kwisatz@rubis.org>
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      c53aeca0