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>,
Doug Smythies <dsmythies@telus.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Giovanni Gherdovich <ggherdovich@suse.cz>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCH v2] cpuidle: Add 'above' and 'below' idle state metrics
Date: Wed, 12 Dec 2018 10:46:10 +0100 [thread overview]
Message-ID: <20181212094610.GW5289@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAJZ5v0jvbDCCgy=nUfb-yZCYGOxe4-XexbvnmeBm8ZPDPBaK4w@mail.gmail.com>
On Tue, Dec 11, 2018 at 10:51:48AM +0100, Rafael J. Wysocki wrote:
> On Mon, Dec 10, 2018 at 11:51 PM Peter Zijlstra <peterz@infradead.org> wrote:
> > Dunno; it could be cold cachelines, at which point it can be fairly
> > expensive. Also, being stuck with API is fairly horrible if you want to
> > 'fix' it.
>
> All of the cache lines involved should've been touched earlier in this
> code path by the governor. At least menu and the new one both touch
> them.
>
> The API part I'm not too worried about. I know it is useful and two
> other people have told that to me already. :-)
Like said on IRC; I mostly wanted to raise the issue of overhead due to
stats and ABI -- it's something I've been bitten by too many times :/
If you're confident you're hitting the same lines with the already
extant accouning (time and usage) and you cannot make the whole lot
conditional because of ABI (bah) then I'll not stand in the way here.
I agree the numbers are useful, I'm just weary of overhead.
next prev parent reply other threads:[~2018-12-12 9:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 11:30 Rafael J. Wysocki
2018-12-10 12:21 ` Peter Zijlstra
2018-12-10 21:36 ` Rafael J. Wysocki
2018-12-10 22:51 ` Peter Zijlstra
2018-12-11 9:51 ` Rafael J. Wysocki
2018-12-12 9:46 ` Peter Zijlstra [this message]
2018-12-12 9:57 ` Ulf Hansson
2018-12-12 10:17 ` Rafael J. Wysocki
2018-12-11 7:28 ` Doug Smythies
2019-01-10 9:52 ` Daniel Lezcano
2019-01-10 10:20 ` Rafael J. Wysocki
2019-01-14 10:39 ` Daniel Lezcano
2019-01-14 23:33 ` Rafael J. Wysocki
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=20181212094610.GW5289@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.lezcano@linaro.org \
--cc=dsmythies@telus.net \
--cc=ggherdovich@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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
Powered by JetHome