From: "Kazlauskas, Nicholas" <nicholas.kazlauskas@amd.com>
To: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Cc: "Harry Wentland" <harry.wentland@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Daniel Vetter" <daniel@ffwll.ch>,
hersenxs.wu@amd.com
Subject: Re: [PATCH v2 1/4] drm/amd/display: Rework registers tracepoint
Date: Fri, 11 Sep 2020 13:13:30 -0400 [thread overview]
Message-ID: <c1eacedd-056d-d6a8-0407-2dea63f47bd9@amd.com> (raw)
In-Reply-To: <20200911145927.401322-2-Rodrigo.Siqueira@amd.com>
On 2020-09-11 10:59 a.m., Rodrigo Siqueira wrote:
> amdgpu_dc_rreg and amdgpu_dc_wreg are very similar, for this reason,
> this commits abstract these two events by using DECLARE_EVENT_CLASS and
> create an instance of it for each one of these events.
>
> Signed-off-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
This looks reasonable to me. Does this still show up as
amdpgu_dc_rrreg/amdgpu_dc_wreg in the captured trace log?
As long as we can still tell this apart you can consider this patch:
Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Regards,
Nicholas Kazlauskas
> ---
> .../amd/display/amdgpu_dm/amdgpu_dm_trace.h | 55 ++++++++-----------
> 1 file changed, 24 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_trace.h b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_trace.h
> index d898981684d5..dd34e11b1079 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_trace.h
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_trace.h
> @@ -31,40 +31,33 @@
>
> #include <linux/tracepoint.h>
>
> -TRACE_EVENT(amdgpu_dc_rreg,
> - TP_PROTO(unsigned long *read_count, uint32_t reg, uint32_t value),
> - TP_ARGS(read_count, reg, value),
> - TP_STRUCT__entry(
> - __field(uint32_t, reg)
> - __field(uint32_t, value)
> - ),
> - TP_fast_assign(
> - __entry->reg = reg;
> - __entry->value = value;
> - *read_count = *read_count + 1;
> - ),
> - TP_printk("reg=0x%08lx, value=0x%08lx",
> - (unsigned long)__entry->reg,
> - (unsigned long)__entry->value)
> -);
> +DECLARE_EVENT_CLASS(amdgpu_dc_reg_template,
> + TP_PROTO(unsigned long *count, uint32_t reg, uint32_t value),
> + TP_ARGS(count, reg, value),
>
> -TRACE_EVENT(amdgpu_dc_wreg,
> - TP_PROTO(unsigned long *write_count, uint32_t reg, uint32_t value),
> - TP_ARGS(write_count, reg, value),
> - TP_STRUCT__entry(
> - __field(uint32_t, reg)
> - __field(uint32_t, value)
> - ),
> - TP_fast_assign(
> - __entry->reg = reg;
> - __entry->value = value;
> - *write_count = *write_count + 1;
> - ),
> - TP_printk("reg=0x%08lx, value=0x%08lx",
> - (unsigned long)__entry->reg,
> - (unsigned long)__entry->value)
> + TP_STRUCT__entry(
> + __field(uint32_t, reg)
> + __field(uint32_t, value)
> + ),
> +
> + TP_fast_assign(
> + __entry->reg = reg;
> + __entry->value = value;
> + *count = *count + 1;
> + ),
> +
> + TP_printk("reg=0x%08lx, value=0x%08lx",
> + (unsigned long)__entry->reg,
> + (unsigned long)__entry->value)
> );
>
> +DEFINE_EVENT(amdgpu_dc_reg_template, amdgpu_dc_rreg,
> + TP_PROTO(unsigned long *count, uint32_t reg, uint32_t value),
> + TP_ARGS(count, reg, value));
> +
> +DEFINE_EVENT(amdgpu_dc_reg_template, amdgpu_dc_wreg,
> + TP_PROTO(unsigned long *count, uint32_t reg, uint32_t value),
> + TP_ARGS(count, reg, value));
>
> TRACE_EVENT(amdgpu_dc_performance,
> TP_PROTO(unsigned long read_count, unsigned long write_count,
>
next prev parent reply other threads:[~2020-09-11 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 14:59 [PATCH v2 0/4] Enlarge tracepoints in the display component Rodrigo Siqueira
2020-09-11 14:59 ` [PATCH v2 1/4] drm/amd/display: Rework registers tracepoint Rodrigo Siqueira
2020-09-11 17:13 ` Kazlauskas, Nicholas [this message]
2020-09-11 14:59 ` [PATCH v2 2/4] drm/amd/display: Add tracepoint for amdgpu_dm Rodrigo Siqueira
2020-09-11 14:59 ` [PATCH v2 3/4] drm/amd/display: Add pipe_state tracepoint Rodrigo Siqueira
2020-09-11 17:11 ` Kazlauskas, Nicholas
2020-09-11 14:59 ` [PATCH v2 4/4] drm/amd/display: Add tracepoint for capturing clocks state Rodrigo Siqueira
2020-09-16 9:12 ` [PATCH v2 0/4] Enlarge tracepoints in the display component Daniel Vetter
2020-09-16 15:27 ` Kazlauskas, Nicholas
2020-09-17 11:36 ` Daniel Vetter
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=c1eacedd-056d-d6a8-0407-2dea63f47bd9@amd.com \
--to=nicholas.kazlauskas@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=hersenxs.wu@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sunpeng.li@amd.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®