From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CDAE2C4361B for ; Tue, 8 Dec 2020 15:04:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A81BE239D1 for ; Tue, 8 Dec 2020 15:04:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730045AbgLHPEA (ORCPT ); Tue, 8 Dec 2020 10:04:00 -0500 Received: from mail.kernel.org ([198.145.29.99]:60416 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729963AbgLHPD7 (ORCPT ); Tue, 8 Dec 2020 10:03:59 -0500 Date: Tue, 8 Dec 2020 07:03:09 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1607439789; bh=or1DcCapyMZAKhkw6/vP2TDxE1YfQnLkxL6zq42F2js=; h=From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=aeauVlPdyqN7Wev4D/DKw8dA5uKQphqz58QLydTXHAAW40ucaXta5MhCDVQMm/ZNN EbCQ7avmA+j5nl2K2z8Cbh1PftPqaxW4yYzel3EO7IpZWQ1aaZ6r6sZxQiwznHcFdx kciyO1GDch/6fW6IJE3QjJ9mYPKWCkphPQl586eBEIOb+s8+5C4wxEN3gePy+9Qo8X ZqCGt6KlTaKSG+v1WpQSrWYWeXRbCMxwWPH8c3DyUQyKe2eoDkUqrtrWn53WOvOHxU 6tgGTK/C8SQSv8NNy65P/j7kCRXqlUAHxkBzaxhIrLQC7tky374Rg9RyQWhcl8o6UE ++KeByZtXs43Q== From: "Paul E. McKenney" To: Peter Zijlstra Cc: Marco Elver , Thomas Gleixner , LKML , kasan-dev , Ingo Molnar , Frederic Weisbecker , Will Deacon , Naresh Kamboju , syzbot+23a256029191772c2f02@syzkaller.appspotmail.com, syzbot+56078ac0b9071335a745@syzkaller.appspotmail.com, syzbot+867130cb240c41f15164@syzkaller.appspotmail.com Subject: Re: [patch 3/3] tick: Annotate tick_do_timer_cpu data races Message-ID: <20201208150309.GP2657@paulmck-ThinkPad-P72> Reply-To: paulmck@kernel.org References: <20201206211253.919834182@linutronix.de> <20201206212002.876987748@linutronix.de> <20201207120943.GS3021@hirez.programming.kicks-ass.net> <87y2i94igo.fsf@nanos.tec.linutronix.de> <20201207194406.GK2657@paulmck-ThinkPad-P72> <20201208081129.GQ2414@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201208081129.GQ2414@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 08, 2020 at 09:11:29AM +0100, Peter Zijlstra wrote: > On Mon, Dec 07, 2020 at 11:44:06AM -0800, Paul E. McKenney wrote: > > > Also, in this particular case, why data_race() rather than READ_ONCE()? > > Do we really expect the compiler to be able to optimize this case > > significantly without READ_ONCE()? > > It's about intent and how the code reads. READ_ONCE() is something > completely different from data_race(). data_race() is correct here. Why? Thanx, Paul