From: Joseph Myers <joseph@codesourcery.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: [PATCH 07/15] Use semget syscall for Linux implementation
Date: Tue, 01 Nov 2016 16:41:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611011638350.21300@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87bmxzw6wn.fsf@linux-m68k.org>
On Tue, 1 Nov 2016, Andreas Schwab wrote:
> On Nov 01 2016, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
>
> > This patch add a direct call to semget syscall if it is defined by
> > kernel headers.
>
> That does not mean that the running kernel provides it.
Specifically, this sort of patch series needs to be accompanied by an
analysis of when the relevant syscalls were added for each supported
architecture (and subarchitecture for cases with multiple syscall tables
for different ABNs). If present (in the syscall table as well as in
asm/unistd.h) in the minimum kernel version, OK, otherwise you need
appropriate __ASSUME_* conditionals (even if not present in the latest
kernel, it might be added in future, so you should have those conditionals
now to avoid breaking things when current glibc is compiled with future
kernel headers).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-01 16:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 14:25 [PATCH 00/15] Consolidate Linux sysvipc implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 12/15] Consolidate Linux shmctl implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 02/15] Consolidate Linux msgrcv implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 11/15] Use shmat syscall for Linux implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 03/15] Use msgsnd " Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 07/15] Use semget " Adhemerval Zanella
2016-11-01 15:34 ` Andreas Schwab
2016-11-01 16:41 ` Joseph Myers [this message]
2016-11-01 17:17 ` Adhemerval Zanella
2016-11-01 17:28 ` Zack Weinberg
2016-11-01 17:35 ` Joseph Myers
2016-11-01 14:25 ` [PATCH 13/15] Use shmdt syscall for linux implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 10/15] Add SYSV semaphore test Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 15/15] Add SYSV shared memory test Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 14/15] Use shmget syscall for linux implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 09/15] Consolidate Linux semtimedop implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 01/15] Consolidate Linux msgctl implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 05/15] Add SYSV message queue test Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 04/15] Use msgget syscall for Linux implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 06/15] Consolidate Linux semctl implementation Adhemerval Zanella
2016-11-01 14:25 ` [PATCH 08/15] Use semop syscall for Linux implementation Adhemerval Zanella
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=alpine.DEB.2.20.1611011638350.21300@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).