From: Chanwoo Choi <cw00.choi@samsung.com>
To: Lukasz Luba <l.luba@partner.samsung.com>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Cc: b.zolnierkie@samsung.com, myungjoo.ham@samsung.com,
kyungmin.park@samsung.com, m.szyprowski@samsung.com,
s.nawrocki@samsung.com, mka@chromium.org, rostedt@goodmis.org,
mingo@redhat.com
Subject: Re: [PATCH v3 1/2] trace: events: add devfreq trace event file
Date: Tue, 19 Feb 2019 09:25:52 +0900 [thread overview]
Message-ID: <aef5a336-779f-3e9d-ec4e-cea1d78f7c09@samsung.com> (raw)
In-Reply-To: <1550514069-9237-2-git-send-email-l.luba@partner.samsung.com>
Hi Lukasz,
On 19. 2. 19. 오전 3:21, Lukasz Luba wrote:
> The patch adds a new file for with trace events for devfreq
> framework. They are used for performance analysis of the framework.
> It also contains updates in MAINTAINERS file adding new entry for
> devfreq maintainers.
>
> Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>
> ---
> MAINTAINERS | 1 +
> include/trace/events/devfreq.h | 40 ++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 41 insertions(+)
> create mode 100644 include/trace/events/devfreq.h
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 41ce5f4..9c44076 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4447,6 +4447,7 @@ S: Maintained
> F: drivers/devfreq/
> F: include/linux/devfreq.h
> F: Documentation/devicetree/bindings/devfreq/
> +F: include/trace/events/devfreq.h
>
> DEVICE FREQUENCY EVENT (DEVFREQ-EVENT)
> M: Chanwoo Choi <cw00.choi@samsung.com>
> diff --git a/include/trace/events/devfreq.h b/include/trace/events/devfreq.h
> new file mode 100644
> index 0000000..cf5b877
> --- /dev/null
> +++ b/include/trace/events/devfreq.h
> @@ -0,0 +1,40 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#undef TRACE_SYSTEM
> +#define TRACE_SYSTEM devfreq
> +
> +#if !defined(_TRACE_DEVFREQ_H) || defined(TRACE_HEADER_MULTI_READ)
> +#define _TRACE_DEVFREQ_H
> +
> +#include <linux/devfreq.h>
> +#include <linux/tracepoint.h>
> +
> +TRACE_EVENT(devfreq_monitor,
> + TP_PROTO(struct devfreq *devfreq),
> +
> + TP_ARGS(devfreq),
> +
> + TP_STRUCT__entry(
> + __field(unsigned long, freq)
> + __field(unsigned long, busy_time)
> + __field(unsigned long, total_time)
> + __field(unsigned int, polling_ms)
> + __string(dev_name, dev_name(&devfreq->dev))
> + ),
> +
> + TP_fast_assign(
> + __entry->freq = devfreq->previous_freq;
> + __entry->busy_time = devfreq->last_status.busy_time;
> + __entry->total_time = devfreq->last_status.total_time;
> + __entry->polling_ms = devfreq->profile->polling_ms;
> + __assign_str(dev_name, dev_name(&devfreq->dev));
> + ),
> +
> + TP_printk("dev_name=%s freq=%lu polling_ms=%u load=%lu",
> + __get_str(dev_name), __entry->freq, __entry->polling_ms,
> + __entry->total_time == 0 ? 0 :
> + (100 * __entry->busy_time) / __entry->total_time)
> +);
> +#endif /* _TRACE_DEVFREQ_H */
> +
> +/* This part must be outside protection */
> +#include <trace/define_trace.h>
>
I think that it is necessary for devfreq. Looks good to me.
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
--
Best Regards,
Chanwoo Choi
Samsung Electronics
next prev parent reply other threads:[~2019-02-19 0:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190218182128eucas1p1bac39e9f11572143697b5cb854b2eb87@eucas1p1.samsung.com>
2019-02-18 18:21 ` [PATCH v3 0/2] tracing: drivers: devfreq: add basic trace mechanism Lukasz Luba
[not found] ` <CGME20190218182129eucas1p236fc8ccddd9a8cde25c15f7545276885@eucas1p2.samsung.com>
2019-02-18 18:21 ` [PATCH v3 1/2] trace: events: add devfreq trace event file Lukasz Luba
2019-02-19 0:25 ` Chanwoo Choi [this message]
[not found] ` <CGME20190218182129eucas1p1804530445570fc73af89ed46b9a448b9@eucas1p1.samsung.com>
2019-02-18 18:21 ` [PATCH v3 2/2] drivers: devfreq: add tracing for scheduling work Lukasz Luba
2019-02-19 0:28 ` Chanwoo Choi
[not found] ` <CGME20190218182129eucas1p236fc8ccddd9a8cde25c15f7545276885@epcms1p7>
2019-02-21 4:21 ` [PATCH v3 1/2] trace: events: add devfreq trace event file MyungJoo Ham
[not found] ` <CGME20190218182129eucas1p1804530445570fc73af89ed46b9a448b9@epcms1p1>
2019-02-21 4:26 ` [PATCH v3 2/2] drivers: devfreq: add tracing for scheduling work MyungJoo Ham
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=aef5a336-779f-3e9d-ec4e-cea1d78f7c09@samsung.com \
--to=cw00.choi@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=l.luba@partner.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mingo@redhat.com \
--cc=mka@chromium.org \
--cc=myungjoo.ham@samsung.com \
--cc=rostedt@goodmis.org \
--cc=s.nawrocki@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®