[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o8b5b05z.ffs@nanos.tec.linutronix.de>
Date: Wed, 14 Jul 2021 13:32:56 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Peter Zijlstra <peterz@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Juri Lelli <juri.lelli@...hat.com>,
Steven Rostedt <rostedt@...dmis.org>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Will Deacon <will@...nel.org>,
Waiman Long <longman@...hat.com>,
Boqun Feng <boqun.feng@...il.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Davidlohr Bueso <dave@...olabs.net>
Subject: Re: [patch 05/50] sched: Provide schedule point for RT locks
On Wed, Jul 14 2021 at 12:17, Peter Zijlstra wrote:
> On Wed, Jul 14, 2021 at 11:49:47AM +0200, Thomas Gleixner wrote:
>> On Wed, Jul 14 2021 at 10:28, Peter Zijlstra wrote:
>> >
>> > #define SM_MASK_STATE (~0U)
>> >
>> > Be even better?
>>
>> SM_MASK_STATE is overengineered. See combo patch 4+5 below
>
> Yep, that should result in similar code as my proposal, thanks!
>
> nit: you like UINT_MAX better than (~0U) ?
No strong preference.
Powered by blists - more mailing lists