From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
Vincent Guittot <vincent.guittot@linaro.org>,
Steven Rostedt <rostedt@goodmis.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Juri Lelli <juri.lelli@arm.com>,
Patrick Bellasi <patrick.bellasi@arm.com>
Subject: Re: [RFC PATCH 4/5] sched/events: Introduce sched_entity load tracking trace event
Date: Wed, 29 Mar 2017 22:19:30 +0200 [thread overview]
Message-ID: <28a1712d-a60d-3870-0c2b-2ebe55c9e61b@arm.com> (raw)
In-Reply-To: <20170328164110.gcejuwpelhhiblpv@hirez.programming.kicks-ass.net>
On 03/28/2017 06:41 PM, Peter Zijlstra wrote:
> On Tue, Mar 28, 2017 at 04:13:45PM +0200, Dietmar Eggemann wrote:
>
>> Do you think that making them public in include/linux/sched.h is the way to
>> go?
>
> No; all that stuff should really stay private. tracepoints are a very
> bad reason to leak this stuff.
Understood & makes sense to me. In hindsight, it's not too complicated
to code group_cfs_rq in include/trace/events/sched.h.
next prev parent reply other threads:[~2017-03-29 20:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 6:35 [RFC PATCH 0/5] CFS load tracking trace events Dietmar Eggemann
2017-03-28 6:35 ` [RFC PATCH 1/5] sched/autogroup: Define autogroup_path() for !CONFIG_SCHED_DEBUG Dietmar Eggemann
2017-03-28 6:35 ` [RFC PATCH 2/5] sched/events: Introduce cfs_rq load tracking trace event Dietmar Eggemann
2017-03-28 7:56 ` Peter Zijlstra
2017-03-28 13:30 ` Dietmar Eggemann
2017-03-28 8:00 ` Peter Zijlstra
2017-03-28 14:47 ` Steven Rostedt
2017-03-28 14:46 ` Steven Rostedt
2017-03-28 16:44 ` Peter Zijlstra
2017-03-28 16:57 ` Peter Zijlstra
2017-03-28 17:20 ` Patrick Bellasi
2017-03-28 18:18 ` Peter Zijlstra
2017-03-28 17:36 ` Steven Rostedt
2017-03-28 17:37 ` Steven Rostedt
2017-03-29 20:37 ` Dietmar Eggemann
2017-03-29 21:03 ` Dietmar Eggemann
2017-03-30 7:04 ` Peter Zijlstra
2017-03-30 7:46 ` Dietmar Eggemann
2017-03-28 6:35 ` [RFC PATCH 3/5] sched/fair: Export group_cfs_rq() Dietmar Eggemann
2017-03-28 6:35 ` [RFC PATCH 4/5] sched/events: Introduce sched_entity load tracking trace event Dietmar Eggemann
2017-03-28 8:05 ` Peter Zijlstra
2017-03-28 14:01 ` Dietmar Eggemann
2017-03-28 14:03 ` Dietmar Eggemann
2017-03-28 8:08 ` Peter Zijlstra
2017-03-28 14:13 ` Dietmar Eggemann
2017-03-28 16:41 ` Peter Zijlstra
2017-03-29 20:19 ` Dietmar Eggemann [this message]
2017-03-28 6:35 ` [RFC PATCH 5/5] sched/events: Introduce task_group " Dietmar Eggemann
2017-03-28 10:05 ` [RFC PATCH 0/5] CFS load tracking trace events Vincent Guittot
2017-03-28 13:45 ` Dietmar Eggemann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28a1712d-a60d-3870-0c2b-2ebe55c9e61b@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=patrick.bellasi@arm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.