Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2600917yba; Mon, 6 May 2019 08:35:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqy4FgP0KzPFZqs1MIljzaWu3KzPNbnLLuBEqv+Kz7FOhKjMSkss3bOfe8P679rR569Jnh++ X-Received: by 2002:a65:6541:: with SMTP id a1mr31733464pgw.233.1557156946550; Mon, 06 May 2019 08:35:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557156946; cv=none; d=google.com; s=arc-20160816; b=hEuXsjlWRP9U+voVm/vsix0iQKZNPjvudyPra1HYB9XCXyghWmNUiNAFQqS5IcOG0v dLYZJMxnYV55sWJdU8W4wP93HSMmQsXyGsnd3kUkMEZmQm01jDRjxU18Pzh0LsHuylRq DO3LBCl9prl/plW0KHDDFlLb2TuBEgXp4EOZ4zWUuDxhHUNRP0exde4l4FnirqGOc00u /oUtviqeAlaN8eMqOtcIe0qRQxuH56dCFQ0MjiTdxNifaQeJdoP7O5H+56zIjRLnGNon A7JLUzx2H6BARgBvve15+Tph7TeID51NWhRgjBl4L+VDB0cu0rhvxxirxUSuxUD75+WO jzIw== 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; bh=DffNerxziLsb1H3cjj+Yrtf66bKuYNUwPEiC7K44Rrk=; b=zhb/uX/CR9n3tLtmb+8Y/4F7eRAsXhBDMKNiXDRyQdN6d3oFFY/kTKUutgWr3uFICo GJXXEnH0rd0y0gjze9zbjTRISfDIVNWRoeUfD2PAzFPaGd7bxGZY3OWFYb3UH18ydAnn VSxvfeR0tY+CQh9txQ34ZGWTWhm+soPACO0ReW0ob0tN1F1qSUEtjPta2DkkL+VM7F8n Yv2O0LT7q9ulZqX869xX7F+8YG9Evq4mK+pbrCyuPlr8966OkDWT76t+KK1IrUNNDtjL kz62FNjID5t4KY3uD0S3wz07kfHJcI1tn3XicMOanrEq7i72Q2JXKLqGO/GY9u0XPtx4 vw+w== 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 w189si13891717pgd.534.2019.05.06.08.35.30; Mon, 06 May 2019 08:35:46 -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 S1726590AbfEFPdW (ORCPT + 99 others); Mon, 6 May 2019 11:33:22 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:54480 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725994AbfEFPdW (ORCPT ); Mon, 6 May 2019 11:33:22 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B0528374; Mon, 6 May 2019 08:33:21 -0700 (PDT) Received: from e107158-lin.cambridge.arm.com (e107158-lin.cambridge.arm.com [10.1.194.71]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 58C383F575; Mon, 6 May 2019 08:33:20 -0700 (PDT) Date: Mon, 6 May 2019 16:33:17 +0100 From: Qais Yousef To: Steven Rostedt Cc: Peter Zijlstra , Ingo Molnar , linux-kernel@vger.kernel.org, Pavankumar Kondeti , Sebastian Andrzej Siewior , Uwe Kleine-Konig Subject: Re: [PATCH 4/7] sched: Add sched_load_rq tracepoint Message-ID: <20190506153317.fv73wpdwsn7xcyc4@e107158-lin.cambridge.arm.com> References: <20190505115732.9844-1-qais.yousef@arm.com> <20190505115732.9844-5-qais.yousef@arm.com> <20190506090859.GK2606@hirez.programming.kicks-ass.net> <20190506095239.08577b3e@gandalf.local.home> <20190506144200.z4s63nm7untol2tr@e107158-lin.cambridge.arm.com> <20190506104618.2fa49e13@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190506104618.2fa49e13@gandalf.local.home> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/06/19 10:46, Steven Rostedt wrote: > On Mon, 6 May 2019 15:42:00 +0100 > Qais Yousef wrote: > > > I can control that for the wrappers I'm introducing. But the actual tracepoint > > get the 'trace_' part prepended automatically by the macros. > > > > ie DECLARE_TRACE(pelt_rq, ...) will automatically generate a function called > > trace_pelt_se(...) > > > > Or am I missing something? > > No trace comes from the trace points. If you want I can do something like below to help create a distinction. It is none enforcing though. diff --git a/include/linux/tracepoint.h b/include/linux/tracepoint.h index 9c3186578ce0..f654ced20045 100644 --- a/include/linux/tracepoint.h +++ b/include/linux/tracepoint.h @@ -232,6 +232,7 @@ static inline struct tracepoint *tracepoint_ptr_deref(tracepoint_ptr_t *p) */ #define __DECLARE_TRACE(name, proto, args, cond, data_proto, data_args) \ extern struct tracepoint __tracepoint_##name; \ + static inline void tp_##name(proto) __alias(trace_##name); \ static inline void trace_##name(proto) \ { \ if (static_key_false(&__tracepoint_##name.key)) \ Another option is to extend DECLARE_TRACE() to take a new argument IS_TP and based on that select the function name. This will be enforcing but I will have to go fixup many places. Of course 'TP' can be replaced with anything more appealing. -- Qais Yousef