[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9447358d3f7cda9032b24d62dd79dacfca73fc30.camel@perches.com>
Date: Fri, 20 Apr 2018 12:24:32 -0700
From: Joe Perches <joe@...ches.com>
To: yuankuiz@...eaurora.org, Thomas Gleixner <tglx@...utronix.de>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Linux PM <linux-pm@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Frederic Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
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, akpm@...ux-foundation.org
Subject: Re: [PATCH] time: tick-sched: use bool for tick_stopped
On Fri, 2018-04-20 at 14:44 +0800, yuankuiz@...eaurora.org wrote:
> On 2018-04-20 09:47 AM, yuankuiz@...eaurora.org wrote:
[]
> > [ZJ] Further prototyping has been given based on gcc for both of
> > x86_64 and armv8-a,
> > unsigned int and bool share the same 1 bytes without the
> > addtional storage for sure.
> > Open this and welcome if any other difference behaviour could be
> > captured.
>
> [ZJ] Typo.. change 4 bytes above to 1 byte actually.
Not really.
unsigned int is 4 and bool is generally 1.
Alignment padding after a bool may exist.
Powered by blists - more mailing lists