From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Patrick Bellasi <patrick.bellasi@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH] cpufreq: schedutil: Always trace frequency if it does not change
Date: Wed, 22 Mar 2017 15:21:16 +0100 [thread overview]
Message-ID: <20170322142116.qpe2faqwbmlmhft7@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAJZ5v0jFDQ9fxHwVWM_Dg-Or5y6o_YJ5=sdyQDZ3Dt0U2bqy_A@mail.gmail.com>
On Wed, Mar 22, 2017 at 01:52:04PM +0100, Rafael J. Wysocki wrote:
> On Wed, Mar 22, 2017 at 10:29 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> > So why not fix the tools?
>
> Because I can't.
>
> I just can't go and fix all of the tools binaries that people use out
> there and I want them to use recent kernels at the same time.
>
Thing is; you're now letting random tracepoint user dictate kernel
implementation. That's a bad state to be in.
(and why I hate tracepoint to begin with)
next prev parent reply other threads:[~2017-03-22 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 0:56 [PATCH] cpufreq: schedutil: Always trace frequency if it does not change Rafael J. Wysocki
2017-03-22 4:16 ` Viresh Kumar
2017-03-22 9:29 ` Peter Zijlstra
2017-03-22 9:56 ` Viresh Kumar
2017-03-22 12:52 ` Rafael J. Wysocki
2017-03-22 14:05 ` Rafael J. Wysocki
2017-03-22 14:21 ` Peter Zijlstra [this message]
2017-03-22 17:13 ` Rafael J. Wysocki
2017-03-22 17:32 ` [PATCH v2] cpufreq: schedutil: Trace frequency only if it has changed Rafael J. Wysocki
2017-03-23 4:32 ` Viresh Kumar
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=20170322142116.qpe2faqwbmlmhft7@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=patrick.bellasi@arm.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox