From: Thomas Gleixner <tglx@linutronix.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Nick Piggin <npiggin@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [rfc][patch] futex: restartable futex_wait?
Date: Fri, 09 Mar 2007 00:02:31 +0100 [thread overview]
Message-ID: <1173394952.24738.1070.camel@localhost.localdomain> (raw)
In-Reply-To: <20070308172902.GA16834@elte.hu>
On Thu, 2007-03-08 at 18:29 +0100, Ingo Molnar wrote:
> * Nick Piggin <npiggin@suse.de> wrote:
>
> > Hi Ingo,
> >
> > I'm seeing an LTP test fail for ltp test sigaction_16_24. Basically,
> > it tests whether the SA_RESTART flag works for the sem_wait operation.
Not sure, whether the testcase is correct or not. See below
> > I see sem_wait is implemented with futex_wait, so I wonder whether we
> > can make it restartable? Am I going about it the right way? (Seems to
> > fix the testcase here).
>
> i think that's quite right. I'm wondering why this never came up before?
> But your fix is not complete i think:
>
> > + restart->arg2 = time;
> > + return -ERESTART_RESTARTBLOCK;
> > + }
>
> 'time' here is relative, so the restarted syscall will do a /full/ wait
> again.
>
> maybe we should rather convert futex timed-waits to hrtimers? Thomas?
The problem is that the original API is based on relative time and
therefor can not be changed.
sem_wait returns -EINTR to the application when it is interrupted, while
pthread_mutex_lock does not.
http://www.opengroup.org/onlinepubs/009695399/functions/sem_wait.html
http://www.opengroup.org/onlinepubs/009695399/functions/pthread_mutex_lock.html
We need to create a seperate op for the futex - just like the pi_futex
and use absolute time there too.
tglx
next prev parent reply other threads:[~2007-03-08 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 15:33 Nick Piggin
2007-03-08 17:29 ` Ingo Molnar
2007-03-08 23:02 ` Thomas Gleixner [this message]
2007-03-09 5:15 ` Nick Piggin
2007-03-09 5:10 ` Nick Piggin
2007-03-09 9:38 ` Thomas Gleixner
2007-03-09 12:24 ` Nick Piggin
2007-03-09 13:10 ` Thomas Gleixner
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=1173394952.24738.1070.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
/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
all inboxes | Powered by JetHome®