From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH] time: tick-sched: use bool for tick_stopped Date: Fri, 20 Apr 2018 12:24:32 -0700 Message-ID: <9447358d3f7cda9032b24d62dd79dacfca73fc30.camel@perches.com> References: <891d4f632fbff5052e11f2d0b6fac35d@codeaurora.org> <2f7755fae34bb65ef0a4b5a11c67f431@codeaurora.org> <41aec3337f05316de118357fcbd9d175@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <41aec3337f05316de118357fcbd9d175@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org To: yuankuiz@codeaurora.org, Thomas Gleixner Cc: "Rafael J. Wysocki" , Linux PM , "Rafael J. Wysocki" , Frederic Weisbecker , Peter Zijlstra , Ingo Molnar , Len Brown , Linux Kernel Mailing List , linux-pm-owner@vger.kernel.org, akpm@linux-foundation.org List-Id: linux-pm@vger.kernel.org On Fri, 2018-04-20 at 14:44 +0800, yuankuiz@codeaurora.org wrote: > On 2018-04-20 09:47 AM, yuankuiz@codeaurora.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.