Received: by 10.192.165.148 with SMTP id m20csp5258565imm; Tue, 1 May 2018 11:46:48 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqS2+InmP5f65XZ7g6XbYG1+pUKucck+f8E/FrogBKddw9d3mqnptKbQsYv7fgrdp+qeNuo X-Received: by 10.98.159.21 with SMTP id g21mr16325839pfe.207.1525200408912; Tue, 01 May 2018 11:46:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525200408; cv=none; d=google.com; s=arc-20160816; b=rpHMYHWmRQdKpet521uhV267bTXbErZCY55+WV/2drCmRxmMuFSjs/BP5DecCs8OZn MehDc0/clMSQnUmu0V1JOBrZU5ys6cG5bPHBTwjwFNuweBOJF4Zrce5dWGmoD6ZgH+zp AFKJvP8OkSpOvSrWrSU4Lq17mndFMQz+dAqw+9/Qq/HH/W+QZLUfDdjY0gXN7wE7eY0r NPaobxHdBf6BLFv6aQs1U8BkI5zBB6UEQI4hef7yTzcbbKjdKBtndCRw2jbhMVQgeQiu tgo/+zip1l980/M/6dE6rnMFwbQ5PlrBtpUERYPoLttG2Qo+GBsnveeKWba0EEfDenD/ uaOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dmarc-filter:arc-authentication-results; bh=I8kznfEmnarhkdHBKIUWD7b6zMkN71g0j5pLc1ml9x4=; b=MVjfOhma9Nkp6W1Ikwh//BMO8FJuppjCmOwLnPP9r4gyFEAOj3Vd1bAeNeUemN8+h9 pJXNAKmqKRhBOQ+N3zUJBaH5k897S2Z/QJmyQ9DCZLZ+b9tKuANXgTDFk3LCbd25xXjC KYHLP3ofcFeG9zJ43NKB/ZQ+Qpy+tkNsSOCV8cI9HQLWGO6MD96/X0HZXGmEtWdQuMjq udqewR7UeZSlx2XRyPX7sjM40ADQmMqsHwIuGeMYK3IhFLdr8wgEJrOMBDTg2muho+qE ftAoT+QnxKkkZrZnHZwnBhrH7QIyLbCWvrcnokPSUUK8YVeE+i8yMGY7DgRuX18HHKLe hb5w== 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 89-v6si10022182plc.444.2018.05.01.11.46.34; Tue, 01 May 2018 11:46:48 -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 S1756494AbeEASqX (ORCPT + 99 others); Tue, 1 May 2018 14:46:23 -0400 Received: from mail.kernel.org ([198.145.29.99]:46294 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756398AbeEASqW (ORCPT ); Tue, 1 May 2018 14:46:22 -0400 Received: from gandalf.local.home (cpe-66-24-56-78.stny.res.rr.com [66.24.56.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B92CE236F6; Tue, 1 May 2018 18:46:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B92CE236F6 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Tue, 1 May 2018 14:46:20 -0400 From: Steven Rostedt To: Nicholas Piggin , Peter Zijlstra Cc: Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [PATCH] tracing/irqtrace: only call trace_hardirqs_on/off when state changes Message-ID: <20180501144620.1e832a09@gandalf.local.home> In-Reply-To: <20171116161506.19691-1-npiggin@gmail.com> References: <20171116161506.19691-1-npiggin@gmail.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 17 Nov 2017 02:15:06 +1000 Nicholas Piggin wrote: > In local_irq_save and local_irq_restore, only call irq tracing when > the flag state acutally changes. It is not unexpected for the state > to go disable->disable. > > This allows the irq tracing code to better track superfluous > enables and disables, and in future could issue warnings. For the > most part they are harmless, but they can indicate that the caller > has lost track of its irq state. I missed this before (that was a busy time, I missed a lot of emails then :-/ ). Anyway, this makes sense. Peter? -- Steve > > Cc: Steven Rostedt > Cc: Ingo Molnar > Cc: linux-kernel@vger.kernel.org > Signed-off-by: Nicholas Piggin > --- > I wonder what you think of this patch? After a small fix to > init/main.c and some powerpc fixes, I was able to use this patch > and a change to warn in the lockdep code in case of redundant ops, > to verify there were no local_irq_enable() when enabled, or > local_irq_disable() when disabled (which was implicated in a bug). > > Lots of code to verify so we can't do this immediately, but I > think it's cleaner to enforce the rule? > > Thanks, > Nick > > include/linux/irqflags.h | 9 ++++++--- > 1 file changed, 6 insertions(+), 3 deletions(-) > > diff --git a/include/linux/irqflags.h b/include/linux/irqflags.h > index 46cb57d5eb13..82287e1c6c52 100644 > --- a/include/linux/irqflags.h > +++ b/include/linux/irqflags.h > @@ -110,7 +110,8 @@ do { \ > #define local_irq_save(flags) \ > do { \ > raw_local_irq_save(flags); \ > - trace_hardirqs_off(); \ > + if (!raw_irqs_disabled_flags(flags)) \ > + trace_hardirqs_off(); \ > } while (0) > > > @@ -118,9 +119,11 @@ do { \ > do { \ > if (raw_irqs_disabled_flags(flags)) { \ > raw_local_irq_restore(flags); \ > - trace_hardirqs_off(); \ > + if (!irqs_disabled()) \ > + trace_hardirqs_off(); \ > } else { \ > - trace_hardirqs_on(); \ > + if (irqs_disabled()) \ > + trace_hardirqs_on(); \ > raw_local_irq_restore(flags); \ > } \ > } while (0)