From: Pavel Machek <pavel@denx.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@redhat.com>,
Douglas Anderson <dianders@chromium.org>,
linux-pm@vger.kernel.org,
Amit Kucheria <amit.kucheria@linaro.org>,
linux-kernel@vger.kernel.org,
Ravi Chandra Sadineni <ravisadineni@chromium.org>
Subject: Re: [PATCH v1] PM / Domains: Add tracepoints
Date: Wed, 2 Oct 2019 21:10:23 +0200 [thread overview]
Message-ID: <20191002191023.GD13492@amd> (raw)
In-Reply-To: <20191001193701.GD87296@google.com>
[-- Attachment #1: Type: text/plain, Size: 2403 bytes --]
On Tue 2019-10-01 12:37:01, Matthias Kaehlcke wrote:
> On Tue, Oct 01, 2019 at 02:08:46PM -0400, Steven Rostedt wrote:
> > On Tue, 1 Oct 2019 10:42:35 -0700
> > Matthias Kaehlcke <mka@chromium.org> wrote:
> >
> > > On Tue, Oct 01, 2019 at 01:03:43PM -0400, Steven Rostedt wrote:
> > > > On Tue, 1 Oct 2019 09:35:42 -0700
> > > > Matthias Kaehlcke <mka@chromium.org> wrote:
> > > >
> > > > > How about this instead:
> > > > >
> > > > > Add tracepoints for genpd_power_on, genpd_power_off and
> > > > > genpd_set_performance_state. The tracepoints can help with
> > > > > understanding power domain behavior of a given device, which
> > > > > may be particularly interesting for battery powered devices
> > > > > and suspend/resume.
> > > >
> > > > Do you have a use case example to present?
> > >
> > > TBH I'm not looking into a specific use case right now. While
> > > peeking around in /sys/kernel/debug/tracing/events to learn more
> > > about existing tracepoints that might be relevant for my work
> > > I noticed the absence of genpd ones and it seemed a good idea to
> > > add them preemptively. Conceptually they seem similar to the
> > > existing regulator_enable/disable and cpu_idle tracepoints.
> > >
> > > As an abstract use case I could see power analysis on battery
> > > powered devices during suspend. genpd_power_on/off allow to see
> > > which power domains remain on during suspend, and might give
> > > insights for possible power saving options. Examples could be that
> > > a power domain stays unexpectedly on due to a misconfiguration, or
> > > two power domains remain on when it could be only one if you just
> > > moved that one pin/port over to the other domain in the next
> > > hardware revision.
> >
> > If the power management maintainers have no issues with adding these,
> > then neither do I ;-) It would be them who would pull them in anyway.
>
> Ok, I'll send a new version with the changes you suggested and some more
> info in the commit message, unless PM maintainers raise concerns before
> that.
Dunno. Adding tracepoints because someone might need them for, umm,
something... I'd wait until they are actually needed.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-10-02 19:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 22:04 [PATCH v1] PM / Domains: Add tracepoints Matthias Kaehlcke
2019-09-27 5:36 ` Greg Kroah-Hartman
2019-09-27 8:42 ` Steven Rostedt
2019-10-01 16:35 ` Matthias Kaehlcke
2019-10-01 17:03 ` Steven Rostedt
2019-10-01 17:42 ` Matthias Kaehlcke
2019-10-01 18:08 ` Steven Rostedt
2019-10-01 19:37 ` Matthias Kaehlcke
2019-10-02 7:55 ` Rafael J. Wysocki
2019-10-02 19:10 ` Pavel Machek [this message]
2019-10-15 12:37 ` Ulf Hansson
2019-10-15 17:19 ` Matthias Kaehlcke
2019-10-16 13:47 ` Ulf Hansson
2019-10-16 18:13 ` Matthias Kaehlcke
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=20191002191023.GD13492@amd \
--to=pavel@denx.de \
--cc=amit.kucheria@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mka@chromium.org \
--cc=ravisadineni@chromium.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.org \
--cc=ulf.hansson@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.