Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4172162imm; Mon, 6 Aug 2018 18:48:15 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcUn7oAXmAanozcxddurb9OSS1jbK1ZPxwKtDOBuemn/V+SAxEZmEZInpgcchHaqFkZb2Wp X-Received: by 2002:a62:6746:: with SMTP id b67-v6mr19603891pfc.243.1533606495760; Mon, 06 Aug 2018 18:48:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533606495; cv=none; d=google.com; s=arc-20160816; b=iDJTZB3bOO0fvNX8nRA6mlrwOEGvQ8ODYKBPqUn423jZJsH6SMFxs5jQE8+k1sRmik og2XnYraCJ0/wgASmI/KkmrB2VIbZwtKLIINrVcI558JwEFcfvLnVvNlw+hJcIND4GoT UTpgovAfGTZ3HNvoKH6xkomO/uOnfhpkYdhSm7fJwd+QMCWyb82luyMLa/vl5hiEJPvc s4cASzj4oOJIaWAjwc3gBzy1I8lnZ3SPDFy2rvYbCG71gSKttsDnSD0ldv64uSEkFnaV JisIFdo73LR+EVZT3VIXg+je4sRn8ic1rHWTUEo8egIuM48N/swSdJIM6LPg+NDYQdbz JpUw== 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 :arc-authentication-results; bh=rL6xlfAI69EElVgoCKL6YndC1V86kjkKjsdM7CnvpIY=; b=YNE5mYby9CMLViH3BhkqefOFPw5CDGJaNkhD6Lncp7Fx9h0QnVdai9X87e22FO2fzp QgalEHTLBsR8v2TR19u2Ml0VC60YG/zSm82MBoTkEPFyY9FRe1knqG/CApCx4BAr3/Y1 2sAejWk0ePYIey4+kpwndRH+a6J8kzpzWfIaXnOriuO181dnhrsiA8Jd/s2obxMvM40u M96O1Q5dK6eqQa6H3ww/BOBx8PjmEdm3zyux/LVwg4+L5MaFJJO29mg4zc4wp5UfkwpQ anOiyfn971sBdjPb7VracwGXfBjRaOA72bRjkMTxldrlhDikZCsROcOXYUZG616rSkod ALsQ== 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 g27-v6si42307pgm.208.2018.08.06.18.47.38; Mon, 06 Aug 2018 18:48:15 -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 S2387469AbeHGDy4 (ORCPT + 99 others); Mon, 6 Aug 2018 23:54:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:49678 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729786AbeHGDy4 (ORCPT ); Mon, 6 Aug 2018 23:54:56 -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 6DF6821A6A; Tue, 7 Aug 2018 01:43:02 +0000 (UTC) Date: Mon, 6 Aug 2018 21:43:00 -0400 From: Steven Rostedt To: Joel Fernandes Cc: Joel Fernandes , LKML , "Cc: Android Kernel" , Boqun Feng , Byungchul Park , Ingo Molnar , Masami Hiramatsu , Mathieu Desnoyers , Namhyung Kim , Paul McKenney , Peter Zijlstra , Thomas Glexiner , Tom Zanussi Subject: Re: [PATCH v12 3/3] tracing: Centralize preemptirq tracepoints and unify their usage Message-ID: <20180806214300.13e63523@gandalf.local.home> In-Reply-To: References: <20180730222423.196630-1-joel@joelfernandes.org> <20180730222423.196630-4-joel@joelfernandes.org> <20180806155058.5ee875f4@gandalf.local.home> 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 Mon, 6 Aug 2018 17:43:19 -0700 Joel Fernandes wrote: > On Mon, Aug 6, 2018 at 12:50 PM, Steven Rostedt wrote: > > > > With this patch applied, I'm constantly getting lockdep errors. Instead > > of doing a full revert of the patch, I did this, which makes all those > > errors go away. I may apply this for now, and we can revisit having > > lockdep use the tracepoint code. But since it's currently always > > enabled, I'm thinking of just leaving this as is. The macros are still > > clean from Joel's patch. > > > > Thoughts? > > I like your patch. Thanks a lot for doing this.. It keeps most of the > benefits of my patch while avoiding the issues with lockdep. I agree > we can look at the remaining lockdep issue after. There were several > lockdep issues with this patch that I fixed over the the months, but > there's still the one that Masami reported that I believe you're also > seeing. Once I'm back I'll work on figuring that one out. > > Could you pull in the fixes to the other issues I posted though? With > that we should be good. > https://lore.kernel.org/patchwork/patch/971104/ > https://lore.kernel.org/patchwork/patch/971829/ > I already had these applied when I created this patch ;-) Thanks, I'll add it. -- Steve