public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@osdl.org>, Arnd Bergmann <arnd@arndb.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
	torvalds@osdl.org, ak@suse.de, linux-arch@vger.kernel.org
Subject: Re: [PATCH] Revert [i386/x86_64]: Remove __KERNEL__ ifdef around _syscall*()
Date: Mon, 4 Sep 2006 21:56:39 +0200	[thread overview]
Message-ID: <200609042156.40143.arnd@arndb.de> (raw)
In-Reply-To: <20060904123801.905fabc6.akpm@osdl.org>

Am Monday 04 September 2006 21:38 schrieb Andrew Morton:
> I think we're working on removing the _syscall() things altogether.  The
> main problem is execve() and I have a series from Arnd queued up to fix
> execve.
>
> I think that there are some remaining uses after execve, but I'm not sure
> what they are.  Arnd, do you recall?

My patch series removed all users in the kernel.

The reason I backed out from removing _syscallX() along with it was
that it is still controversial whether it has any value to user space.

Andi's point was that it is an essential part of the kernel ABI and
we should not break existing source using these macros, especially
since the alternative syscall() function provided by glibc has been
frequently broken in the past on x86.

HPA made the point that syscall() from glibc is by design inefficient
on some architectures, so there may be reasons to use _syscallX() instead.

There are lots of arguments in favor of removing them.

	Arnd <><

  reply	other threads:[~2006-09-04 19:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200608302359.k7UNxIZW027536@hera.kernel.org>
2006-09-04 19:27 ` [PATCH] Revert [i386/x86_64]: Remove __KERNEL__ ifdef around _syscall*() David Woodhouse
2006-09-04 19:38   ` Andrew Morton
2006-09-04 19:56     ` Arnd Bergmann [this message]
2006-09-04 20:50       ` David Woodhouse
2006-09-04 19:56     ` David Woodhouse
2006-09-10  9:48     ` David Woodhouse
2006-09-10  8:33       ` Andi Kleen
2006-09-10 10:30         ` David Woodhouse
2006-09-04 20:07   ` Arnd Bergmann
2006-09-04 20:30   ` Andi Kleen
2006-09-04 21:16     ` David Woodhouse

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=200609042156.40143.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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