[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87sf94m222.ffs@tglx>
Date: Mon, 31 Jul 2023 19:19:17 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Peter Zijlstra <peterz@...radead.org>, axboe@...nel.dk
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org,
mingo@...hat.com, dvhart@...radead.org, dave@...olabs.net,
andrealmeid@...lia.com, Andrew Morton <akpm@...ux-foundation.org>,
urezki@...il.com, hch@...radead.org, lstoakes@...il.com,
Arnd Bergmann <arnd@...db.de>, linux-api@...r.kernel.org,
linux-mm@...ck.org, linux-arch@...r.kernel.org,
malteskarupke@....de
Subject: Re: [PATCH v1 09/14] futex: Add sys_futex_requeue()
On Fri, Jul 21 2023 at 12:22, Peter Zijlstra wrote:
> +/*
> + * sys_futex_requeue - Requeue a waiter from one futex to another
> + * @waiters: array describing the source and destination futex
> + * @flags: unused
> + * @nr_wake: number of futexes to wake
> + * @nr_requeue: number of futexes to requeue
> + *
> + * Identical to the traditional FUTEX_CMP_REQUEUE op, except it is part of the
> + * futex2 family of calls.
> + */
> +
> +SYSCALL_DEFINE4(futex_requeue,
> + struct futex_waitv __user *, waiters,
> + unsigned int, flags,
> + int, nr_wake,
> + int, nr_requeue)
> +{
> + struct futex_vector futexes[2];
> + u32 cmpval;
So this is explictely u32. I'm completely confused vs. the 64 bit futex
size variant enablement earlier in the series by now.
Powered by blists - more mailing lists