Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2628433yba; Mon, 6 May 2019 09:03:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqxLSXZn+VMAyUhDi7nBBKBs/PO2jB0Dc+vZCy7PPqjh0HLRsAUfACET65QTiHKfi5D6+ITp X-Received: by 2002:aa7:8c1a:: with SMTP id c26mr34175689pfd.25.1557158592500; Mon, 06 May 2019 09:03:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557158592; cv=none; d=google.com; s=arc-20160816; b=QeCr8oeAsy0WFUk/E47xgMqUlMXMl4V0VHRDnmrNvhKs5sTgPLye+mYfTU/FJaAhn9 icVXe/8L+MqGrNMkY/2rGNRDWwfkbtF9sy1zY1Ovul6CBRaNiY0isr5Mz2649sC8c8ry LduNT70/nUHUboU7SxvzU+/uNnoFokrBjEdb9OiYqCAsk/4eJFLOk3sGRC2+vK5j1s7k K2mVvuULrR4cNE9cVN0wFF2jmNrWjqfKlUCBkPha2AzTiF0ldFwu87rvPrJPVVg3qasV WGSmIdQzDCKoB4R44tQYXQixWm8ymJm0+xU1bx5jRWEZKy6SeGrW4NXq9dUbkUp6xUo2 UPyw== 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; bh=q9pii2SviAI0OXB+mHx1zH36oNs9uKDOhde+/XLuO1Q=; b=M8IYlXCEOguBLs4EWkYRnfjKVJC3y4itqfBhDinKbnDnP1oJqM83JneGUsLCjDTy9K 2/TZxhKIBnzEZtbGrovfgqSx/8fTjAmVYJCaCLudnFzcUXsE1nghan73+jQXZNimh6b/ E+cwuyC1L5uVN6Jj3j6w0x1vud2Kmm8sfSgzeoWmz0HFIOGyYePIwsImaenoUmHkME1h hh19ugO8TMQh8QGpcEJqw57A79LY8gtJ0dBTSl3Wh/QzGapOfbntzlwGbvJEdAqcj/qm 3f+Jp28iKnjSB7vhppGK/BSu0wd5ypmes/wG4icCDV22+Uok6uEIHWh3zsZwJCZsFw0C E6+Q== 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 e1si17037449pln.52.2019.05.06.09.02.55; Mon, 06 May 2019 09:03:12 -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 S1726814AbfEFQBW (ORCPT + 99 others); Mon, 6 May 2019 12:01:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:33080 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725994AbfEFQBW (ORCPT ); Mon, 6 May 2019 12:01:22 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (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 D0E2620578; Mon, 6 May 2019 16:01:20 +0000 (UTC) Date: Mon, 6 May 2019 12:01:19 -0400 From: Steven Rostedt To: Qais Yousef 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: <20190506120119.12d98042@gandalf.local.home> In-Reply-To: <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> <20190506153317.fv73wpdwsn7xcyc4@e107158-lin.cambridge.arm.com> X-Mailer: Claws Mail 3.17.3 (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 May 2019 16:33:17 +0100 Qais Yousef wrote: > 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. Re-reading that line, I see I totally didn't express what I meant :-p > > 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. No no no, I meant to say... "No that's OK. The "trace_" *is* from the trace points, and trace events build on top of them." -- Steve