Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5025979yba; Wed, 8 May 2019 06:50:12 -0700 (PDT) X-Google-Smtp-Source: APXvYqzI10sMe3599NzfIbhAgdVVXVApYfRuMs/b6HmjP2MHzgEhmq5ZsWgsJZwONQ4A+Wc7F1GC X-Received: by 2002:aa7:99c7:: with SMTP id v7mr49170026pfi.103.1557323412668; Wed, 08 May 2019 06:50:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557323412; cv=none; d=google.com; s=arc-20160816; b=lUIdFBb+YlFes5MX/mQfynsgqdbiw4rgfYt7wMZVMbiasHMR7a3h1fn35XmwMmZH+T YGLjUIToNZQ9SsrbSZdNXcw0+dRiHagTvgh4ujYJGnz2+KRV5iGnxOudwT5xfU23bHtG qXHFjj5rpJNMrkl1tyL8aTS59nmDVJ0vH4nYdUONAF9ObFppXO2MRInKTRIDaID+rNUA FCtBNOmn0pKeKewR6oJanQeOpp712wfHgiAB+LkaB4Igf/jTgmt/xNCBcQzEw1gUrfWl w3PP+iHYoh5vYRYjzGozVww5O30HosdFxrZlwno8752aXn0eYTMza3DSdjROeKd3r/V7 dkgw== 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=Q+uP03V7G5TDTmCc9+m7FzB1RwMZ4F5bxQafeZoAgQk=; b=U3Ooh2c2jGnhE9Y+YV8afpj/ee8WXewZauDWfvOUpva/C/7epsdEI35r0t0t/f5xY0 +o8nqSL8iey4JsM6uZJi3klER5GPW/F29B5VjGcTYpAbvJDwHZlvm58+XfDT0JOu1FMn 4M45UtIxK/anpO/+AFo2bg+cPM1di+BsFdLPC6CdpYiMWC/39JmyZDXp+GPsHYpm6uO/ +b0XP2KeFQu66b6gvhwMcUJwIiH4KqFjxrNW28WKhOXAnvYHnfijlA/1JPUR6Qnx0vKp W+kbCl7aOA6m1r0YaJmaBmxutunGLyfmLh52vE3BzfKVLDpAVVbZFzCH3ciY59Oln23H dtEw== 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 l7si24758097plb.245.2019.05.08.06.49.56; Wed, 08 May 2019 06:50: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 S1727515AbfEHNiX (ORCPT + 99 others); Wed, 8 May 2019 09:38:23 -0400 Received: from foss.arm.com ([217.140.101.70]:34668 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726803AbfEHNiX (ORCPT ); Wed, 8 May 2019 09:38:23 -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 27A5280D; Wed, 8 May 2019 06:38:23 -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 C0FD83F5AF; Wed, 8 May 2019 06:38:21 -0700 (PDT) Date: Wed, 8 May 2019 14:38:18 +0100 From: Qais Yousef To: Peter Zijlstra Cc: Ingo Molnar , Steven Rostedt , 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: <20190508133818.hvgc537fpnlnefwe@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> <20190506091823.GF2650@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190506091823.GF2650@hirez.programming.kicks-ass.net> 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 11:18, Peter Zijlstra wrote: > On Mon, May 06, 2019 at 11:08:59AM +0200, Peter Zijlstra wrote: > > Also; I _really_ hate how fat they are. Why can't we do simple straight > > forward things like: > > > > trace_pelt_cfq(cfq); > > trace_pelt_rq(rq); > > trace_pelt_se(se); > > > > And then have the thing attached to the event do the fat bits like > > extract the path and whatnot. > > ARGH, because we don't export any of those data structures (for good > reason).. bah I hate all this. I am not a big fan either.. FWIW struct sched_entity and struct sched_avg are exported but only used in kernel/sched/*. Are the reasons behind not exporting struct cfs_rq and struct rq are really different to the other 2? Anyways. I have v2 almost ready but thought I'd ask before posting if we want to handle this in a different way. Thanks -- Qais Yousef