lkml.org 
[lkml]   [2010]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: asm-generic/unistd.h and glibc use of NR_ipc
On Tue, 28 Sep 2010, Arnd Bergmann wrote:

> Once the kernel parts are upstream and use the generic syscall ABI, only
> rudimentary architecture support in glibc would be needed.

In my experience very little of a glibc port relates to the particular set
of syscalls present on a particular architecture (and what does often
consists of one-line files that #include the file for i386 or some other
convenient architecture); changing a port from an old syscall ABI to the
generic one would mean making it use the new set of generic files in
preference to some existing sysdeps/unix/sysv/linux files, and maybe
having fewer bits/ headers if some of the architecture differences there
are avoided, but no real differences to any of the bits that aren't purely
mechanical such as the implementation of each architecture's TLS ABI,
other pieces of the ELF ABI, the set of atomic operations available,
startup code, longjmp, profiling, clone, the interface used to call an
individual syscall, etc. - remember that you can't build any vaguely
recent glibc without full shared library and NPTL support.

A lot of the *changes made to maintain an existing port* relate to
constants in the duplicated bits/* headers which it might be good to
duplicate less if future architectures share values for all the constants,
but that's not where most of the complexity in the port lies. MIPS is
probably the worst case for code dealing with syscall ABI peculiarities
(given the three different ABIs, and n64 having different userspace stat
and stat64 structures), but even there they aren't much of a source of
complexity (MIPS ELF peculiarities are much more an issue).
--
Joseph S. Myers
joseph@codesourcery.com


\
 
 \ /
  Last update: 2010-09-28 18:45    [from the cache]
©2003-2011 Jasper Spaans