Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3385087pxk; Mon, 7 Sep 2020 11:19:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyfoczGJ/vV9g9lpsLPUk8ALbxQO4ZE/Hks8kw/N++vpCGa+BUvBtA6tJD0hreCrHJZEog7 X-Received: by 2002:aa7:cb8f:: with SMTP id r15mr23724935edt.356.1599502782499; Mon, 07 Sep 2020 11:19:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599502782; cv=none; d=google.com; s=arc-20160816; b=tQz3ZB5o9egb1AdszuhPsRaI5NPkG3ke0gKHwD5Wy49hdt8wfDXt8ByrGg+YsP8GLx jJaxvGKLwvnbMA6cC4riE+9ms9xKapkjitiD/Grl771CzKPdADa8LNVvnS1z+xAP7JOW v14n+V4YSqw56IQ0sZel+sPzX38QprtErIjR0ZDYReKQulbpq+bE2S0WgBv5XswDXXSU 9rix/o+vpYe/5JdzRTkqtPxst6tIrTtH55WaVRlsDi4dkw2LuMBzAr/R1dEUnkxoboOH uBGnwrWH2s199C9+Rq618f62Sj77xYJ4cJZr8ByWkZbZh6qOq2qMPyIYwavS/yR/ARjj 7A5A== 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=s6jY90FplzxbIYrafAH1FyfYq3XxoPy4qomWmar8KzY=; b=RWe3xEPc4FNWmgdY7G8YSyKexBamkVNNzbvGPwA7xPRmixHt2gllQF7gSr0UXGzMz5 3Vgw9p8nO9AuZpH9OZZhTlgex2bCJR03kerAbiRaUhRNpGOYnM+rJiWHUvNpqPQSNS5e gOTBfN2Ulmy5pxYtH82UnBjQsb1enBCe4YBHv+OaG83WxIdDSF6I+zJXiiChwk9qOZme 7xIiktoPx+cRx/7eSYCoAflZPjjRLWtg9cHzLK6aEFnkUVroCnT4dSp9ljOXN/+AI56t qHRh2ckZWIKcUUDKA/r8hAo9UXBUtJdImb8v68rdHtnfxuBBkUwvWG/yF718yV5wGch9 QSOg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x10si10634792ejv.339.2020.09.07.11.19.20; Mon, 07 Sep 2020 11:19:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731361AbgIGR4z (ORCPT + 99 others); Mon, 7 Sep 2020 13:56:55 -0400 Received: from foss.arm.com ([217.140.110.172]:33118 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728649AbgIGLUG (ORCPT ); Mon, 7 Sep 2020 07:20:06 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id C31B911D4; Mon, 7 Sep 2020 04:02:27 -0700 (PDT) Received: from e107158-lin.cambridge.arm.com (e107158-lin.cambridge.arm.com [10.1.195.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A9DF33F66E; Mon, 7 Sep 2020 04:02:26 -0700 (PDT) Date: Mon, 7 Sep 2020 12:02:24 +0100 From: Qais Yousef To: Phil Auld Cc: Dietmar Eggemann , vincent.donnefort@arm.com, mingo@redhat.com, peterz@infradead.org, vincent.guittot@linaro.org, linux-kernel@vger.kernel.org, valentin.schneider@arm.com Subject: Re: [PATCH v2] sched/debug: Add new tracepoint to track cpu_capacity Message-ID: <20200907110223.gtdgqod2iv2w7xmg@e107158-lin.cambridge.arm.com> References: <1598605249-72651-1-git-send-email-vincent.donnefort@arm.com> <20200828102724.wmng7p6je2pkc33n@e107158-lin.cambridge.arm.com> <1e806d48-fd54-fd86-5b3a-372d9876f360@arm.com> <20200828172658.dxygk7j672gho4ax@e107158-lin.cambridge.arm.com> <58f5d2e8-493b-7ce1-6abd-57705e5ab437@arm.com> <20200902135423.GB93959@lorien.usersys.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200902135423.GB93959@lorien.usersys.redhat.com> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/02/20 09:54, Phil Auld wrote: > > > > I think this decoupling is not necessary. The natural place for those > > scheduler trace_event based on trace_points extension files is > > kernel/sched/ and here the internal sched.h can just be included. > > > > If someone really wants to build this as an out-of-tree module there is > > an easy way to make kernel/sched/sched.h visible. > > > > It's not so much that we really _want_ to do this in an external module. > But we aren't adding more trace events and my (limited) knowledge of > BPF let me to the conclusion that its raw tracepoint functionality > requires full events. I didn't see any other way to do it. I did have a patch that allowed that. It might be worth trying to upstream it. It just required a new macro which could be problematic. https://github.com/qais-yousef/linux/commit/fb9fea29edb8af327e6b2bf3bc41469a8e66df8b With the above I could attach using bpf::RAW_TRACEPOINT mechanism. Cheers -- Qais Yousef