public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Avoid cancellation point in pthread_mutex_lock etc. in linuxthreads
Date: Tue, 01 Apr 2003 20:17:00 -0000	[thread overview]
Message-ID: <20030401201745.GM16629@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <200304011950.h31JoPZ23056@magilla.sf.frob.com>

On Tue, Apr 01, 2003 at 11:50:25AM -0800, Roland McGrath wrote:
> Why __pthread_sigsuspend instead of just using INTERNAL_SYSCALL directly?
> kernel-features.h can define something about rt_sigsuspend vs sigsuspend
> for each machine.

It differs between arches.
On most arches it is
INTERNAL_SYSCALL (rt_sigsuspend, err, 2, set, _NSIG / 8);
on some for compatibility
INTERNAL_SYSCALL (sigsuspend, err, 3, 0, 0, set->__val[0]);
(with possible runtime choice) but on Alpha it is
INTERNAL_SYSCALL (sigsuspend, err, 1, set->__val[0]);
(well, looks like the same on sparc32 for pre-rtsig kernels,
apparently nobody is running < 2.2.x kernels on sparc any more).
I think best would be a special header in
linuxthreads/sysdeps/unix/sysv/linux/*
and inline the call to avoid the call/return overhead.

	Jakub

  reply	other threads:[~2003-04-01 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01 15:19 Jakub Jelinek
2003-04-01 19:50 ` Roland McGrath
2003-04-01 20:17   ` Jakub Jelinek [this message]
2003-04-01 20:46     ` Ulrich Drepper
2003-04-02  0:11 ` Roland McGrath

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=20030401201745.GM16629@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).