[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180410112637.GD4082@hirez.programming.kicks-ass.net>
Date: Tue, 10 Apr 2018 13:26:37 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: yuankuiz@...eaurora.org
Cc: Thomas Gleixner <tglx@...utronix.de>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Linux PM <linux-pm@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Len Brown <len.brown@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-pm-owner@...r.kernel.org
Subject: Re: [PATCH] time: tick-sched: use bool for tick_stopped
On Tue, Apr 10, 2018 at 06:07:17PM +0800, yuankuiz@...eaurora.org wrote:
> > > > > @@ -48,8 +48,8 @@ struct tick_sched {
> > > > > unsigned long check_clocks;
> > > > > enum tick_nohz_mode nohz_mode;
> > > > >
> > > > > + bool tick_stopped : 1;
> > > > > unsigned int inidle : 1;
> > > > > - unsigned int tick_stopped : 1;
> > > > > unsigned int idle_active : 1;
> > > > > unsigned int do_timer_last : 1;
> > > > > unsigned int got_idle_tick : 1;
> > > >
> > > > I don't think this is a good idea at all.
> > > >
> > > > Please see https://lkml.org/lkml/2017/11/21/384 for example.
> > > [ZJ] Thanks for this sharing. Looks like, this patch fall into the
> > > case of
> > > "Maybe".
> >
> > This patch falls into the case 'pointless' because it adds extra storage
> [ZJ] 1 bit vs 1 bit. no more.
Since its a different type, the bitfields will not be merged. Also I'm
surprised a bitfield with base-type _Bool is even allowed.
> > for no benefit at all.
> [ZJ] tick_stopped is returned by the tick_nohz_tick_stopped() which is bool.
> The benefit is no any potiential type conversion could be minded.
Do you have any actual evidence for that? Is there a compiler stupid
enough to generate code to convert a bool to a 1bit value?
Powered by blists - more mailing lists