Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1830619imm; Thu, 21 Jun 2018 03:09:38 -0700 (PDT) X-Google-Smtp-Source: ADUXVKI8O3cRa1+Urw6g/2EGfbcSbNlWdnId+EajBzyfBqzVM1aK40eooqQR63fC4cqgBoQqDdVA X-Received: by 2002:a17:902:246a:: with SMTP id m39-v6mr27927105plg.141.1529575778401; Thu, 21 Jun 2018 03:09:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529575778; cv=none; d=google.com; s=arc-20160816; b=aHhQ5evUzKYimCnYG0gs36gWforEv5ym+CVy2BB3Que1a7E5jHD1J2ImYMG1FZ+NW7 oN60o/s9XWv0XHy9GdxvqtIQbsXQXi49JoncUxpeTQ8b1ThCw7cfCa7Oi98R9cnzuGzT KYIHH5SeX79DskuPXDSYCVRfW9RItY8jaY0Yu4PISt20xWuh6BSsdeuYVCr4m1ykLM9j /bNxtJUSDyH4+MLWJi/NFD5M4HOBeShNFh7F1BKZ1FMowruA6EEuel/MDwdRNk1x76HB tvxTS6xOvhY5AztAZx0S7hpI1vreV2aW2c+ZaXegacfdg3F1DpUqFmBQEp/P7caa3TJB IWeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=zbGb37c62DhGc9ld1zvIUB97GgVox0BPZbUwNDMDWKw=; b=w2V7T5/0tWntqIykTqvD3PL4Hgu4a2m4tU4KZVn7GW48kUAXufTmrp8YUNKuApvNTW nEq+23ukGXhfoa1rHhwp6DEkNKIrzlkkEH7MuDr3OFmrxKiHMmI3akdSrCB7TVpKQyuU EnXncunLjAKPPVdSy0lIj/K1WS+jpfpIcbuIrLt+XAiRbvZgdrxdzm+0hcxdqBWqOLmB HDYZlnmxH92dHdOZBfZzQ4UnG7gsNLFuMcwvNuBGpNgpOtu+nW0yQDpWmRZSP3v6BGjm +Ejg3Buj/WTqLZwWh2X3D5dzqnLF/NeSl724YJ0uCvtueh+8yakQlG3zyx0YSqIZ93vH 9Lxg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n1-v6si3530834pge.263.2018.06.21.03.09.23; Thu, 21 Jun 2018 03:09:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932874AbeFUKIg (ORCPT + 99 others); Thu, 21 Jun 2018 06:08:36 -0400 Received: from lgeamrelo13.lge.com ([156.147.23.53]:43620 "EHLO lgeamrelo11.lge.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932677AbeFUKIf (ORCPT ); Thu, 21 Jun 2018 06:08:35 -0400 Received: from unknown (HELO lgeamrelo04.lge.com) (156.147.1.127) by 156.147.23.53 with ESMTP; 21 Jun 2018 19:08:32 +0900 X-Original-SENDERIP: 156.147.1.127 X-Original-MAILFROM: byungchul.park@lge.com Received: from unknown (HELO X58A-UD3R) (10.177.222.33) by 156.147.1.127 with ESMTP; 21 Jun 2018 19:08:32 +0900 X-Original-SENDERIP: 10.177.222.33 X-Original-MAILFROM: byungchul.park@lge.com Date: Thu, 21 Jun 2018 19:08:30 +0900 From: Byungchul Park To: "Paul E. McKenney" Cc: Byungchul Park , jiangshanlai@gmail.com, josh@joshtriplett.org, Steven Rostedt , Mathieu Desnoyers , linux-kernel@vger.kernel.org, kernel-team@lge.com, Joel Fernandes , luto@kernel.org Subject: Re: [RFC 2/2] rcu: Remove ->dynticks_nmi_nesting from struct rcu_dynticks Message-ID: <20180621100830.GC28024@X58A-UD3R> References: <1529484440-20634-1-git-send-email-byungchul.park@lge.com> <1529484440-20634-2-git-send-email-byungchul.park@lge.com> <20180620145814.GQ3593@linux.vnet.ibm.com> <20180620164902.GW3593@linux.vnet.ibm.com> <20180620174037.GZ3593@linux.vnet.ibm.com> <20180621063949.GA28024@X58A-UD3R> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180621063949.GA28024@X58A-UD3R> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 21, 2018 at 03:39:49PM +0900, Byungchul Park wrote: [...] > I applied what you suggested and re-named rcu_nmi_{enter,exit} to ^ rcu_nmi_{enter,exit}_common(bool irq) > rcu_irq_{enter,exit} and applied the same re-naming to ^ rcu_irq_{enter,exit}_common(bool nmi) > ->dynticks_nmi_nesting as well, since those are not things to do with ^ dynticks_nmi_nesting -> dynticks_irq_nesting > nmi anymore but both irq and nmi. > > I think "irq" is better to represent both irq and nmi than "nmi". > Please let me know if you don't think so. I can get rid of the re- > naming from the patch. -- Thanks, Byungchul