From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756604AbcHVVQC (ORCPT ); Mon, 22 Aug 2016 17:16:02 -0400 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:53018 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754416AbcHVVQB (ORCPT ); Mon, 22 Aug 2016 17:16:01 -0400 X-IBM-Helo: d03dlp01.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com Date: Mon, 22 Aug 2016 14:16:06 -0700 From: "Paul E. McKenney" To: Geert Uytterhoeven Cc: Steven Rostedt , Peter Zijlstra , Eric Dumazet , LKML , Ingo Molnar , jiangshanlai@gmail.com, dipankar@in.ibm.com, Andrew Morton , Mathieu Desnoyers , Josh Triplett , Thomas Gleixner , David Howells , Darren Hart , =?iso-8859-1?Q?Fr=E9d=E9ric?= Weisbecker , Oleg Nesterov , pranith kumar Subject: Re: [PATCH tip/core/rcu 2/2] documentation: Record reason for rcu_head two-byte alignment Reply-To: paulmck@linux.vnet.ibm.com References: <20160822151413.GA6337@linux.vnet.ibm.com> <1471878883-6660-2-git-send-email-paulmck@linux.vnet.ibm.com> <20160822162553.GJ10153@twins.programming.kicks-ass.net> <20160822173453.GF3482@linux.vnet.ibm.com> <20160822185609.GK10153@twins.programming.kicks-ass.net> <20160822151854.175dfea8@grimm.local.home> <20160822195445.GO3482@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16082221-0004-0000-0000-0000103198C0 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00005630; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000183; SDB=6.00748233; UDB=6.00353105; IPR=6.00520898; BA=6.00004672; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00012425; XFM=3.00000011; UTC=2016-08-22 21:15:57 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 16082221-0005-0000-0000-00007833B0A4 Message-Id: <20160822211606.GU3482@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-08-22_12:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1608220212 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 22, 2016 at 10:48:57PM +0200, Geert Uytterhoeven wrote: > Hi Paul, > > On Mon, Aug 22, 2016 at 9:54 PM, Paul E. McKenney > wrote: > > On Mon, Aug 22, 2016 at 03:18:54PM -0400, Steven Rostedt wrote: > >> On Mon, 22 Aug 2016 20:56:09 +0200 > >> Peter Zijlstra wrote: > >> > >> > > Don't we have __alignof__(void *) to avoid #ifdef CONFIG_M68K and > >> > > other new macros ? > > > > Hmmm... Does __alignof__(void *) give two-byte alignment on m68k, > > allowing something like this? Heh!!! It is already there. ;-) > > > > struct callback_head { > > struct callback_head *next; > > void (*func)(struct callback_head *head); > > } __attribute__((aligned(sizeof(void *)))); > > No, it's aligning to sizeof(void *) (4 on m68k), not __alignof__(void *). Right you are. Commit 720abae3d68ae from Kirill A. Shutemov in November 2015. Given that you haven't complained, I am guessing that this works for you. If so, I can make the __call_rcu() WARN_ON() more strict. > > #define rcu_head callback_head > > > > If so, that does sound quite attractive! Might need the WARN_ON() > > anyway, to flag wild pointers if nothing else. > > > > Adding Geert on CC for his thoughts. > > __alignof__(void *) is indeed 2 on m68k, and h8300. > > Note that it is 1 on crisv32! Gah... ((__alignof__(void *) + 1) & ~0x1), eh? > It's 4 or 8 on anything else I have a cross-compiler for. > > $ cat a.c > unsigned x = __alignof__(void *); > $ for i in /opt/cross/*/*/bin/*gcc; do echo +++ $i +++; $i -c -S a.c; > cat a.s; done | less Thank you for checking! Again, does the current state work for you? Thanx, Paul