The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, eranian@hpl.hp.com, ak@muc.de,
	benh@kernel.crashing.org, paulus@samba.org,
	stephane.eranian@hp.com, tony.luck@intel.com
Subject: Re: + perfmon2-reserve-system-calls.patch added to -mm tree
Date: Mon, 14 Nov 2005 17:12:26 -0800	[thread overview]
Message-ID: <20051114171226.680cddc8.akpm@osdl.org> (raw)
In-Reply-To: <200511150050.27556.arnd@arndb.de>

Arnd Bergmann <arnd@arndb.de> wrote:
>
> >  #ifdef __KERNEL__
> >  #define __NR__exit __NR_exit
> 
> Hmm, I had sent an earlier patch to paulus that reserves 278 and
> 279 for spu_run and spu_create and that apparently got dropped.
> 
> Could I have those two numbers or is there already an established
> user based for the perfmon2 numbers that would take preference?

aargh.  Any time anyone dinks with the syscall tables I have tons of fun
fixing up rejects.  It doesn't help that both Stephane and Christoph's
patches were fairly broken.

Rules:

a) Keep unistd.h and the syscall tables in sync.

b) Keep ppc32 and powerpc[64] in sync

c) Add prototypes to syscalls.h (When the implementation goes in -
   obviously not relevant when we're just reserving syscall slots)

d) Some architectures have multiple syscall tables.  Stephane, you
   missed arch/ia64/ia32/ia32_entry.S, for example.  But then, that looks
   to be seriously out of date anyway.  No idea what's going on there.

e) review your work carefully.  Grep the tree for, say, `getxattr' (or
   any other syscall name which is unique-looking and which you expect all
   architectures to implement).

Anyway, I have a shower of fixup patches here.   Hopefully it all landed OK.

  parent reply	other threads:[~2005-11-15  1:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200511142329.jAENTfmS004600@shell0.pdx.osdl.net>
2005-11-14 23:50 ` + perfmon2-reserve-system-calls.patch added to -mm tree Arnd Bergmann
2005-11-15  0:04   ` Paul Mackerras
2005-11-15  0:09     ` Stephane Eranian
2005-11-15  1:12   ` Andrew Morton [this message]
2005-11-15  8:00     ` Stephane Eranian
2005-11-15  8:08       ` Arjan van de Ven
2005-11-15 13:40         ` Andi Kleen
2005-11-15  9:06   ` Christoph Hellwig
2005-11-16 10:24     ` Stephane Eranian
2005-11-15 15:28 Luck, Tony
2005-11-15 15:49 ` Stephane Eranian
  -- strict thread matches above, loose matches on Subject: below --
2005-11-15 16:58 Luck, Tony

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051114171226.680cddc8.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@muc.de \
    --cc=arnd@arndb.de \
    --cc=benh@kernel.crashing.org \
    --cc=eranian@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=stephane.eranian@hp.com \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox