From: Arnd Bergmann <arnd@arndb.de>
To: linasvepstas@gmail.com
Cc: GLIBC Devel <libc-alpha@sourceware.org>,
linux-kernel@vger.kernel.org, Chris Metcalf <cmetcalf@tilera.com>
Subject: Re: asm-generic/unistd.h and glibc use of NR_ipc
Date: Tue, 28 Sep 2010 10:40:09 +0200 [thread overview]
Message-ID: <201009281040.09728.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTi=33kimswSJ1tYsnG-PVs6Z4dVBtnqq65GN8Vxw@mail.gmail.com>
On Tuesday 28 September 2010, Linas Vepstas wrote:
> I'm trying to figure out the status of glibc w.r.t the latest linux
> unistd syscall interface, specifically, the status of the NR_ipc
> syscall. Currently, I see the following:
>
> -- Circa June 2009, Arnd Bergman introduced asm-generic/unistd.h
> (into the linux kernel) to provide a generic interface to system
> calls. It does *not* define NR_ipc, and instead provides
> NR_msgsnd, msgrcv, msgget, msgctl etc. syscalls.
>
> -- Current glibc (2.12.1, as well as the current eglibc) does
> not appear to use these new calls anywhere. Instead, glibc
> has generic (non-arch-specific) implementations of msgsnd
> etc. that use the old NR_ipc interface (see, e.g.
> sysdeps/unix/sysv/linux/msgsnd.c, semget.c, shmdt.c, msgrcv.c,
> shmget.c, etc.)
>
> Is someone working on patches to get glibc to use the new
> syscall interfaces (for IPC)? Am I missing something? Seems like
> any arch wishing to use asm-generic/unistd.h and get glibc working
> gets to break new ground, here ... right?
Chris Metcalf is using the generic unistd.h file on the tile architecture
and has a glibc port that should be easily portable to all future
architectures. There are a few of them getting ready to be merged
now (c6x, lm32, nios2, and some people have contacted me privately
for architectures I cannot name).
I expect that all of them will just use the same syscall ABI and glibc
port.
Arnd
next prev parent reply other threads:[~2010-09-28 8:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 23:26 asm-generic/unistd.h and glibc use of NR_ipc Linas Vepstas
2010-09-28 0:02 ` Mike Frysinger
2010-09-28 8:40 ` Arnd Bergmann [this message]
2010-09-28 13:05 ` Chris Metcalf
2010-09-28 15:52 ` Joseph S. Myers
2010-09-28 16:13 ` Arnd Bergmann
2010-09-28 16:41 ` Joseph S. Myers
2010-09-28 20:08 ` Arnd Bergmann
2010-09-28 16:50 ` Mike Frysinger
2010-09-28 16:42 ` Mike Frysinger
2010-09-28 16:52 ` Joseph S. Myers
2010-09-28 17:36 ` Linas Vepstas
2010-09-30 13:23 ` Chris Metcalf
2010-09-29 5:16 ` Christoph Hellwig
2010-09-29 11:55 ` Arnd Bergmann
2011-03-10 16:46 ` Linas Vepstas
2011-03-10 17:07 ` Chris Metcalf
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=201009281040.09728.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cmetcalf@tilera.com \
--cc=libc-alpha@sourceware.org \
--cc=linasvepstas@gmail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.