From: Steven Rostedt <rostedt@goodmis.org>
To: Peiyong Lin <lpy@google.com>
Cc: amit.kucheria@linaro.org, android-kernel@google.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, paul.walmsley@sifive.com, pavel@ucw.cz,
prahladk@google.com, rafael.j.wysocki@intel.com,
ulf.hansson@linaro.org, yamada.masahiro@socionext.com
Subject: Re: [PATCH v2] Add power/gpu_frequency tracepoint.
Date: Thu, 13 Aug 2020 17:50:37 -0400 [thread overview]
Message-ID: <20200813175037.48a16064@oasis.local.home> (raw)
In-Reply-To: <20200813213703.153080-1-lpy@google.com>
On Thu, 13 Aug 2020 14:37:03 -0700
Peiyong Lin <lpy@google.com> wrote:
> Historically there is no common trace event for GPU frequency, in
> downstream Android each different hardware vendor implements their own
> way to expose GPU frequency, for example as a debugfs node. This patch
> standardize it as a common trace event in upstream linux kernel to help
> the ecosystem have a common implementation across hardware vendors.
> Toolings in the Linux ecosystem will benefit from this especially in the
> downstream Android, where this information is critical to graphics
> developers.
>
> Signed-off-by: Peiyong Lin <lpy@google.com>
> ---
>
> Changelog since v1:
> - Use %u in TP_printk
>
For just the tracing side of this, but the use case is up for others to do:
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2020-08-13 21:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 21:03 [PATCH] Add power/gpu_frequency tracepoint Peiyong Lin
2020-08-13 21:22 ` Steven Rostedt
2020-08-13 21:37 ` [PATCH v2] " Peiyong Lin
2020-08-13 21:50 ` Steven Rostedt [this message]
2020-08-20 19:41 ` [PATCH v3] " Peiyong Lin
2020-08-20 20:27 ` Steven Rostedt
2020-10-22 16:59 ` [PATCH] " Peiyong Lin
2020-10-22 17:34 ` [PATCH v4] " Peiyong Lin
2020-10-26 22:25 ` Peiyong Lin
2020-10-27 6:16 ` Greg Kroah-Hartman
2020-11-16 20:55 ` Peiyong Lin
2020-11-16 21:05 ` Steven Rostedt
2020-11-17 18:00 ` Rafael J. Wysocki
2020-11-17 18:00 ` Rafael J. Wysocki
2020-11-17 18:10 ` Alex Deucher
2020-11-17 18:10 ` Alex Deucher
2020-11-17 21:31 ` Peiyong Lin
2020-11-17 21:31 ` Peiyong Lin
2020-11-30 22:33 ` Peiyong Lin
2020-11-30 22:33 ` Peiyong Lin
2020-12-02 12:34 ` Brian Starkey
2020-12-02 12:34 ` Brian Starkey
2020-12-21 20:10 ` [PATCH v5] " Peiyong Lin
2020-12-21 20:10 ` Peiyong Lin
2021-03-10 21:56 ` Peiyong Lin
2021-03-10 21:56 ` Peiyong Lin
2021-03-12 18:08 ` Pavel Machek
2021-03-12 18:08 ` Pavel Machek
[not found] ` <159741850487.10342.14268227307882225260@build.alporthouse.com>
2020-08-14 19:25 ` [PATCH] " Peiyong Lin
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=20200813175037.48a16064@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=amit.kucheria@linaro.org \
--cc=android-kernel@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpy@google.com \
--cc=mingo@redhat.com \
--cc=paul.walmsley@sifive.com \
--cc=pavel@ucw.cz \
--cc=prahladk@google.com \
--cc=rafael.j.wysocki@intel.com \
--cc=ulf.hansson@linaro.org \
--cc=yamada.masahiro@socionext.com \
/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.