[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVr7d1QZYaRtAxafD3aJp7GMwKNVqe7HUDykoDjU+OdQg@mail.gmail.com>
Date: Tue, 25 Jul 2023 09:23:29 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: tglx@...utronix.de, axboe@...nel.dk, linux-kernel@...r.kernel.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 1:11 PM Peter Zijlstra <peterz@...radead.org> wrote:
> Finish of the 'simple' futex2 syscall group by adding
> sys_futex_requeue(). Unlike sys_futex_{wait,wake}() it's arguments are
> too numerous to fit into a regular syscall. As such, use struct
> futex_waitv to pass the 'source' and 'destination' futexes to the
> syscall.
>
> This syscall implements what was previously known as FUTEX_CMP_REQUEUE
> and uses {val, uaddr, flags} for source and {uaddr, flags} for
> destination.
>
> This design explicitly allows requeueing between different types of
> futex by having a different flags word per uaddr.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> arch/m68k/kernel/syscalls/syscall.tbl | 1
Acked-by: Geert Uytterhoeven <geert@...ux-m68k.org>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists