On Wed, Oct 07, 2015 at 10:34:19AM +0100, Michael Kerrisk (man-pages) wrote:
> On 08/19/2015 03:40 PM, Thomas Gleixner wrote:
> > On Wed, 5 Aug 2015, Darren Hart wrote:
> >> On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages)
> >> wrote:
> >>> .\" FIXME XXX = Start of
On Wed, Oct 07, 2015 at 09:30:46AM +0100, Michael Kerrisk (man-pages) wrote:
> Hello Thomas,
>
> Thanks for the follow up!
>
> Some open questions below are marked with the string ###.
A couple of comments from me below, although I suspect you have this much
covered already.
>
> On 08/19/2015
On Wed, Oct 07, 2015 at 09:30:46AM +0100, Michael Kerrisk (man-pages) wrote:
> Hello Thomas,
>
> Thanks for the follow up!
>
> Some open questions below are marked with the string ###.
A couple of comments from me below, although I suspect you have this much
covered already.
>
> On 08/19/2015
On Wed, Oct 07, 2015 at 10:34:19AM +0100, Michael Kerrisk (man-pages) wrote:
> On 08/19/2015 03:40 PM, Thomas Gleixner wrote:
> > On Wed, 5 Aug 2015, Darren Hart wrote:
> >> On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages)
> >> wrote:
> >>> .\" FIXME XXX = Start of
On 08/19/2015 03:40 PM, Thomas Gleixner wrote:
> On Wed, 5 Aug 2015, Darren Hart wrote:
>> On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
>>> .\" FIXME XXX = Start of adapted Hart/Guniguntala text =
>>> .\" The following text is drawn from the
Hello Thomas,
Thanks for the follow up!
Some open questions below are marked with the string ###.
On 08/19/2015 04:17 PM, Thomas Gleixner wrote:
> On Sat, 8 Aug 2015, Michael Kerrisk (man-pages) wrote:
FUTEX_CMP_REQUEUE (since Linux 2.6.7)
This operation first
Hello Thomas,
Thanks for the follow up!
Some open questions below are marked with the string ###.
On 08/19/2015 04:17 PM, Thomas Gleixner wrote:
> On Sat, 8 Aug 2015, Michael Kerrisk (man-pages) wrote:
FUTEX_CMP_REQUEUE (since Linux 2.6.7)
This operation first
On 08/19/2015 03:40 PM, Thomas Gleixner wrote:
> On Wed, 5 Aug 2015, Darren Hart wrote:
>> On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
>>> .\" FIXME XXX = Start of adapted Hart/Guniguntala text =
>>> .\" The following text is drawn from the
On Thu, Aug 20, 2015 at 01:17:03AM +0200, Thomas Gleixner wrote:
...
> > >> .\" FIXME XXX In discussing errors for FUTEX_CMP_REQUEUE_PI, Darren Hart
> > >> .\" made the observation that "EINVAL is returned if the non-pi
> > >> .\" to pi or op pairing semantics are violated."
> > >>
On Thu, Aug 20, 2015 at 01:17:03AM +0200, Thomas Gleixner wrote:
...
.\ FIXME XXX In discussing errors for FUTEX_CMP_REQUEUE_PI, Darren Hart
.\ made the observation that EINVAL is returned if the non-pi
.\ to pi or op pairing semantics are violated.
.\ Probably
On Sat, Aug 08, 2015 at 08:57:35AM +0200, Michael Kerrisk (man-pages) wrote:
...
> >> .\" FIXME = End of adapted Hart/Guniguntala text =
> >>
> >>
> >>
> >> .\" FIXME We need some explanation in the following paragraph of *why*
> >> .\" it is important to note that "the kernel will
On Thu, Aug 20, 2015 at 12:40:46AM +0200, Thomas Gleixner wrote:
> On Wed, 5 Aug 2015, Darren Hart wrote:
> > On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
> > > .\" FIXME XXX = Start of adapted Hart/Guniguntala text =
> > > .\" The following text is
On Thu, Aug 20, 2015 at 12:40:46AM +0200, Thomas Gleixner wrote:
On Wed, 5 Aug 2015, Darren Hart wrote:
On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
.\ FIXME XXX = Start of adapted Hart/Guniguntala text =
.\ The following text is drawn from
On Sat, Aug 08, 2015 at 08:57:35AM +0200, Michael Kerrisk (man-pages) wrote:
...
.\ FIXME = End of adapted Hart/Guniguntala text =
.\ FIXME We need some explanation in the following paragraph of *why*
.\ it is important to note that the kernel will update the
.\
On Sat, 8 Aug 2015, Michael Kerrisk (man-pages) wrote:
> >>FUTEX_CMP_REQUEUE (since Linux 2.6.7)
> >> This operation first checks whether the location uaddr
> >> still contains the value val3. If not, the operation
> >> fails with the
On Wed, 5 Aug 2015, Darren Hart wrote:
> On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
> > .\" FIXME XXX = Start of adapted Hart/Guniguntala text =
> > .\" The following text is drawn from the Hart/Guniguntala paper
> > .\" (listed in SEE ALSO),
On Wed, 5 Aug 2015, Darren Hart wrote:
On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
.\ FIXME XXX = Start of adapted Hart/Guniguntala text =
.\ The following text is drawn from the Hart/Guniguntala paper
.\ (listed in SEE ALSO), but I have
On Sat, 8 Aug 2015, Michael Kerrisk (man-pages) wrote:
FUTEX_CMP_REQUEUE (since Linux 2.6.7)
This operation first checks whether the location uaddr
still contains the value val3. If not, the operation
fails with the error
Hi Darren,
Some of my comments below will refer to the reply I just sent
to tglx (and the list) a few minutes ago.
On 08/06/2015 12:21 AM, Darren Hart wrote:
> On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
>> Hello all,
>>
>
> Michael, thank you for your diligence
On 07/28/2015 11:03 PM, Thomas Gleixner wrote:
> On Tue, 28 Jul 2015, Peter Zijlstra wrote:
>
>> On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
>>
FUTEX_WAKE (since Linux 2.6.0)
This operation wakes at most val of the waiters that are
Hi Thomas,
Thank you for the comments below. This helps hugely:
more than 30 of my FIXMEs have now gone away!
I have a few open questions, which you can find
by searching for the string "???". If you would have
a chance to look at those, I'd appreciate it.
On 07/28/2015 10:23 PM, Thomas
Hi Thomas,
Thank you for the comments below. This helps hugely:
more than 30 of my FIXMEs have now gone away!
I have a few open questions, which you can find
by searching for the string ???. If you would have
a chance to look at those, I'd appreciate it.
On 07/28/2015 10:23 PM, Thomas Gleixner
On 07/28/2015 11:03 PM, Thomas Gleixner wrote:
On Tue, 28 Jul 2015, Peter Zijlstra wrote:
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
FUTEX_WAKE (since Linux 2.6.0)
This operation wakes at most val of the waiters that are
waiting
Hi Darren,
Some of my comments below will refer to the reply I just sent
to tglx (and the list) a few minutes ago.
On 08/06/2015 12:21 AM, Darren Hart wrote:
On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
Hello all,
Michael, thank you for your diligence in
On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
> Hello all,
>
Michael, thank you for your diligence in following up and collecting
reviews. I've attempted to respond to what I was specifically called out
in or where I had something specific to add in addition to
On Mon, Jul 27, 2015 at 02:07:15PM +0200, Michael Kerrisk (man-pages) wrote:
Hello all,
Michael, thank you for your diligence in following up and collecting
reviews. I've attempted to respond to what I was specifically called out
in or where I had something specific to add in addition to other
On 07/29/2015 06:21 AM, Darren Hart wrote:
> On Tue, Jul 28, 2015 at 09:11:41PM -0700, Darren Hart wrote:
>> On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
>>> On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
>>
>> ...
>>
FUTEX_REQUEUE (since Linux 2.6.0)
On 07/29/2015 06:21 AM, Darren Hart wrote:
On Tue, Jul 28, 2015 at 09:11:41PM -0700, Darren Hart wrote:
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
...
FUTEX_REQUEUE (since Linux 2.6.0)
.\ FIXME(Torvald) Is
On Tue, 28 Jul 2015, Darren Hart wrote:
> Found it on libc-alpha, here it is for reference:
>
> From: Rich Felker
> Date: Wed, 29 Oct 2014 22:43:17 -0400
> To: Darren Hart
> Cc: Carlos O'Donell , Roland McGrath
> ,
> Torvald Riegel , GLIBC Devel
> ,
>
On Tue, 28 Jul 2015, Darren Hart wrote:
Found it on libc-alpha, here it is for reference:
From: Rich Felker dal...@libc.org
Date: Wed, 29 Oct 2014 22:43:17 -0400
To: Darren Hart dvh...@infradead.org
Cc: Carlos O'Donell car...@redhat.com, Roland McGrath
On Tue, Jul 28, 2015 at 09:11:41PM -0700, Darren Hart wrote:
> On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
> > On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
>
> ...
>
> > >FUTEX_REQUEUE (since Linux 2.6.0)
> > > .\" FIXME(Torvald) Is there some indication
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
> On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
...
> >FUTEX_REQUEUE (since Linux 2.6.0)
> > .\" FIXME(Torvald) Is there some indication that FUTEX_REQUEUE is broken
> > .\" in general, or is this comment
On Tue, 2015-07-28 at 22:45 +0200, Peter Zijlstra wrote:
> Also, this code seems to use plist, which means it won't do the right
> thing for SCHED_DEADLINE either.
Ick, I don't look forward to seeing nice futex plists converted into
rbtrees. As opposed to, eg. rtmutexes, there are a few caveats:
On Tue, 28 Jul 2015, Peter Zijlstra wrote:
> On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
>
> > >FUTEX_WAKE (since Linux 2.6.0)
> > > This operation wakes at most val of the waiters that are
> > > waiting (e.g., inside FUTEX_WAIT) on the
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
> >FUTEX_WAKE (since Linux 2.6.0)
> > This operation wakes at most val of the waiters that are
> > waiting (e.g., inside FUTEX_WAIT) on the futex word at the
> > address uaddr.
On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
>FUTEX_CLOCK_REALTIME (since Linux 2.6.28)
> This option bit can be employed only with the
> FUTEX_WAIT_BITSET and FUTEX_WAIT_REQUEUE_PI operations.
>
> If this option is set,
On Tue, 2015-07-28 at 22:45 +0200, Peter Zijlstra wrote:
Also, this code seems to use plist, which means it won't do the right
thing for SCHED_DEADLINE either.
Ick, I don't look forward to seeing nice futex plists converted into
rbtrees. As opposed to, eg. rtmutexes, there are a few caveats:
-
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
...
FUTEX_REQUEUE (since Linux 2.6.0)
.\ FIXME(Torvald) Is there some indication that FUTEX_REQUEUE is broken
.\ in general, or is this comment implicitly
On Tue, Jul 28, 2015 at 09:11:41PM -0700, Darren Hart wrote:
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
...
FUTEX_REQUEUE (since Linux 2.6.0)
.\ FIXME(Torvald) Is there some indication that
On Tue, 28 Jul 2015, Peter Zijlstra wrote:
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
FUTEX_WAKE (since Linux 2.6.0)
This operation wakes at most val of the waiters that are
waiting (e.g., inside FUTEX_WAIT) on the futex word
On Tue, Jul 28, 2015 at 10:23:51PM +0200, Thomas Gleixner wrote:
FUTEX_WAKE (since Linux 2.6.0)
This operation wakes at most val of the waiters that are
waiting (e.g., inside FUTEX_WAIT) on the futex word at the
address uaddr. Most
On Mon, 27 Jul 2015, Michael Kerrisk (man-pages) wrote:
FUTEX_CLOCK_REALTIME (since Linux 2.6.28)
This option bit can be employed only with the
FUTEX_WAIT_BITSET and FUTEX_WAIT_REQUEUE_PI operations.
If this option is set, the
On 07/27/2015 04:17 PM, Heinrich Schuchardt wrote:
> instruction. A thread maybe unable
>
> to << missing word
>
> acquire a lock because it is
> already acquired by another thread. It then may pass the lock's
> flag as futex word and the value representing the acquired state
> as the expected
Hello all,
>From a draft sent out in March, I got a few useful comments that
I've now incorporated into this draft. And I got some complaints
from people who did not want to read groff source. My point
was that there are a bunch of FIXMEs in the page source that I
wanted people to look at...
Hello all,
From a draft sent out in March, I got a few useful comments that
I've now incorporated into this draft. And I got some complaints
from people who did not want to read groff source. My point
was that there are a bunch of FIXMEs in the page source that I
wanted people to look at...
On 07/27/2015 04:17 PM, Heinrich Schuchardt wrote:
instruction. A thread maybe unable
to missing word
acquire a lock because it is
already acquired by another thread. It then may pass the lock's
flag as futex word and the value representing the acquired state
as the expected value to a
46 matches
Mail list logo
