1. 14 3月, 2016 1 次提交
  2. 11 1月, 2016 2 次提交
  3. 09 2月, 2015 1 次提交
    • H
      avr32: wire up missing syscalls · f3240c1f
      Hans-Christian Egtvedt 提交于
      This patch adds a bunch of missing syscalls to AVR32:
      __NR_pread64
      __NR_pwrite64
      __NR_timerfd_create
      __NR_fallocate
      __NR_timerfd_settime
      __NR_timerfd_gettime
      __NR_signalfd4
      __NR_eventfd2
      __NR_epoll_create1
      __NR_dup3
      __NR_pipe2
      __NR_inotify_init1
      __NR_preadv
      __NR_pwritev
      __NR_rt_tgsigqueueinfo
      __NR_perf_event_open
      __NR_recvmmsg
      __NR_fanotify_init
      __NR_fanotify_mark
      __NR_prlimit64
      __NR_name_to_handle_at
      __NR_open_by_handle_at
      __NR_clock_adjtime
      __NR_syncfs
      __NR_sendmmsg
      __NR_process_vm_readv
      __NR_process_vm_writev
      __NR_kcmp
      __NR_finit_module
      __NR_sched_setattr
      __NR_sched_getattr
      __NR_renameat2
      __NR_seccomp
      __NR_getrandom
      __NR_memfd_create
      __NR_bpf
      __NR_execveat
      
      On AVR32, all parameters beyond the 5th are passed on the stack. System
      calls don't use the stack -- they borrow a callee-saved register
      instead. This means that syscalls that take 6 parameters must be called
      through a stub that pushes the last parameter on the stack.
      
      This relates to syscall fallocate, fanotify_mark, process_vm_readv, and
      process_vm_writev.
      Signed-off-by: NHans-Christian Egtvedt <egtvedt@samfundet.no>
      f3240c1f
  4. 04 2月, 2013 1 次提交
  5. 29 11月, 2012 1 次提交
  6. 15 10月, 2012 1 次提交
  7. 27 8月, 2011 1 次提交
  8. 29 5月, 2011 1 次提交
    • E
      ns: Wire up the setns system call · 7b21fddd
      Eric W. Biederman 提交于
      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 <dlezcano@fr.ibm.com>
      v3: ported to v2.6.36-rc4 by: Eric W. Biederman <ebiederm@xmission.com>
      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: NMike Frysinger <vapier@gentoo.org>
      
      Oh - ia64 wiring looks good.
      Acked-by: NTony Luck <tony.luck@intel.com>
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7b21fddd
  9. 13 10月, 2009 1 次提交
    • A
      net: Introduce recvmmsg socket syscall · a2e27255
      Arnaldo Carvalho de Melo 提交于
      Meaning receive multiple messages, reducing the number of syscalls and
      net stack entry/exit operations.
      
      Next patches will introduce mechanisms where protocols that want to
      optimize this operation will provide an unlocked_recvmsg operation.
      
      This takes into account comments made by:
      
      . Paul Moore: sock_recvmsg is called only for the first datagram,
        sock_recvmsg_nosec is used for the rest.
      
      . Caitlin Bestler: recvmmsg now has a struct timespec timeout, that
        works in the same fashion as the ppoll one.
      
        If the underlying protocol returns a datagram with MSG_OOB set, this
        will make recvmmsg return right away with as many datagrams (+ the OOB
        one) it has received so far.
      
      . Rémi Denis-Courmont & Steven Whitehouse: If we receive N < vlen
        datagrams and then recvmsg returns an error, recvmmsg will return
        the successfully received datagrams, store the error and return it
        in the next call.
      
      This paves the way for a subsequent optimization, sk_prot->unlocked_recvmsg,
      where we will be able to acquire the lock only at batch start and end, not at
      every underlying recvmsg call.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a2e27255
  10. 20 9月, 2008 1 次提交
  11. 06 2月, 2008 1 次提交
  12. 13 5月, 2007 1 次提交
  13. 09 5月, 2007 1 次提交
  14. 16 2月, 2007 2 次提交
  15. 06 11月, 2006 1 次提交
  16. 26 9月, 2006 1 次提交