linux.git/arch/x86/kernel/syscall_table_32.S, branch v2.6.37

x86: fix up system call numbering nit

2010-08-10T22:35:10+00:00

As pointed out by Jiri Slaby: when I resolved the the 32-bit x85 system
call entry tables for prlimit (due to the conflict with fanotify), I
forgot to add the numbering in comments that we do for every fifth entry.

Reported-by: Jiri Slaby 
Signed-off-by: Linus Torvalds

Merge branch 'writable_limits' of git://decibel.fi.muni.cz/~xslaby/linux

2010-08-10T19:07:51+00:00

* 'writable_limits' of git://decibel.fi.muni.cz/~xslaby/linux:
  unistd: add __NR_prlimit64 syscall numbers
  rlimits: implement prlimit64 syscall
  rlimits: switch more rlimit syscalls to do_prlimit
  rlimits: redo do_setrlimit to more generic do_prlimit
  rlimits: add rlimit64 structure
  rlimits: do security check under task_lock
  rlimits: allow setrlimit to non-current tasks
  rlimits: split sys_setrlimit
  rlimits: selinux, do rlimits changes under task_lock
  rlimits: make sure ->rlim_max never grows in sys_setrlimit
  rlimits: add task_struct to update_rlimit_cpu
  rlimits: security, add task_struct to setrlimit

Fix up various system call number conflicts.  We not only added fanotify
system calls in the meantime, but asm-generic/unistd.h added a wait4
along with a range of reserved per-architecture system calls.

fanotify: sys_fanotify_mark declartion

2010-07-28T13:58:55+00:00

This patch simply declares the new sys_fanotify_mark syscall

int fanotify_mark(int fanotify_fd, unsigned int flags, u64_mask,
		  int dfd const char *pathname)

Signed-off-by: Eric Paris

fanotify: fanotify_init syscall declaration

2010-07-28T13:58:55+00:00

This patch defines a new syscall fanotify_init() of the form:

int sys_fanotify_init(unsigned int flags, unsigned int event_f_flags,
		      unsigned int priority)

This syscall is used to create and fanotify group.  This is very similar to
the inotify_init() syscall.

Signed-off-by: Eric Paris

unistd: add __NR_prlimit64 syscall numbers

2010-07-16T07:52:32+00:00

Add __NR_prlimit64 syscall numbers to asm-generic. Add them also to
asm-x86, both 32 and 64-bit.

Signed-off-by: Jiri Slaby 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin"

Add generic sys_old_mmap()

2010-03-12T23:52:32+00:00

Add a generic implementation of the old mmap() syscall, which expects its
argument in a memory block and switch all architectures over to use it.

Signed-off-by: Christoph Hellwig 
Cc: Ralf Baechle 
Cc: Benjamin Herrenschmidt 
Cc: Paul Mundt 
Cc: Jeff Dike 
Cc: Hirokazu Takata 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Reviewed-by: H. Peter Anvin 
Cc: Al Viro 
Cc: Arnd Bergmann 
Cc: Heiko Carstens 
Cc: Martin Schwidefsky 
Cc: "Luck, Tony" 
Cc: James Morris 
Cc: Andreas Schwab 
Acked-by: Jesper Nilsson 
Acked-by: Russell King 
Acked-by: Greg Ungerer 
Acked-by: David Howells 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Add generic sys_old_select()

2010-03-12T23:52:32+00:00

Add a generic implementation of the old select() syscall, which expects
its argument in a memory block and switch all architectures over to use
it.

Signed-off-by: Christoph Hellwig 
Cc: Ralf Baechle 
Cc: Benjamin Herrenschmidt 
Cc: Paul Mundt 
Cc: Jeff Dike 
Cc: Hirokazu Takata 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Reviewed-by: H. Peter Anvin 
Cc: Al Viro 
Cc: Arnd Bergmann 
Cc: Heiko Carstens 
Cc: Martin Schwidefsky 
Cc: "Luck, Tony" 
Cc: James Morris 
Acked-by: Andreas Schwab 
Acked-by: Russell King 
Acked-by: Greg Ungerer 
Acked-by: David Howells 
Cc: Andreas Schwab 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Unify sys_mmap*

2009-12-11T11:44:29+00:00

New helper - sys_mmap_pgoff(); switch syscalls to using it.

Acked-by: David S. Miller 
Signed-off-by: Al Viro

net: Introduce recvmmsg socket syscall

2009-10-13T06:40:10+00:00

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: Arnaldo Carvalho de Melo 
Signed-off-by: David S. Miller

perf: Do the big rename: Performance Counters -> Performance Events

2009-09-21T12:28:04+00:00

Bye-bye Performance Counters, welcome Performance Events!

In the past few months the perfcounters subsystem has grown out its
initial role of counting hardware events, and has become (and is
becoming) a much broader generic event enumeration, reporting, logging,
monitoring, analysis facility.

Naming its core object 'perf_counter' and naming the subsystem
'perfcounters' has become more and more of a misnomer. With pending
code like hw-breakpoints support the 'counter' name is less and
less appropriate.

All in one, we've decided to rename the subsystem to 'performance
events' and to propagate this rename through all fields, variables
and API names. (in an ABI compatible fashion)

The word 'event' is also a bit shorter than 'counter' - which makes
it slightly more convenient to write/handle as well.

Thanks goes to Stephane Eranian who first observed this misnomer and
suggested a rename.

User-space tooling and ABI compatibility is not affected - this patch
should be function-invariant. (Also, defconfigs were not touched to
keep the size down.)

This patch has been generated via the following script:

  FILES=$(find * -type f | grep -vE 'oprofile|[^K]config')

  sed -i \
    -e 's/PERF_EVENT_/PERF_RECORD_/g' \
    -e 's/PERF_COUNTER/PERF_EVENT/g' \
    -e 's/perf_counter/perf_event/g' \
    -e 's/nb_counters/nb_events/g' \
    -e 's/swcounter/swevent/g' \
    -e 's/tpcounter_event/tp_event/g' \
    $FILES

  for N in $(find . -name perf_counter.[ch]); do
    M=$(echo $N | sed 's/perf_counter/perf_event/g')
    mv $N $M
  done

  FILES=$(find . -name perf_event.*)

  sed -i \
    -e 's/COUNTER_MASK/REG_MASK/g' \
    -e 's/COUNTER/EVENT/g' \
    -e 's/\/event_id/g' \
    -e 's/counter/event/g' \
    -e 's/Counter/Event/g' \
    $FILES

... to keep it as correct as possible. This script can also be
used by anyone who has pending perfcounters patches - it converts
a Linux kernel tree over to the new naming. We tried to time this
change to the point in time where the amount of pending patches
is the smallest: the end of the merge window.

Namespace clashes were fixed up in a preparatory patch - and some
stylistic fallout will be fixed up in a subsequent patch.

( NOTE: 'counters' are still the proper terminology when we deal
  with hardware registers - and these sed scripts are a bit
  over-eager in renaming them. I've undone some of that, but
  in case there's something left where 'counter' would be
  better than 'event' we can undo that on an individual basis
  instead of touching an otherwise nicely automated patch. )

Suggested-by: Stephane Eranian 
Acked-by: Peter Zijlstra 
Acked-by: Paul Mackerras 
Reviewed-by: Arjan van de Ven 
Cc: Mike Galbraith 
Cc: Arnaldo Carvalho de Melo 
Cc: Frederic Weisbecker 
Cc: Steven Rostedt 
Cc: Benjamin Herrenschmidt 
Cc: David Howells 
Cc: Kyle McMartin 
Cc: Martin Schwidefsky 
Cc: "David S. Miller" 
Cc: Thomas Gleixner 
Cc: "H. Peter Anvin" 
Cc: 
LKML-Reference: 
Signed-off-by: Ingo Molnar