From: Frank Li <Frank.li@nxp.com>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: will@kernel.org, mark.rutland@arm.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com,
john.g.garry@oracle.com, jolsa@kernel.org, namhyung@kernel.org,
irogers@google.com, mike.leach@linaro.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, adrian.hunter@intel.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
imx@lists.linux.dev
Subject: Re: [PATCH v7 5/8] perf: imx_perf: fix counter start and config sequence
Date: Mon, 18 Mar 2024 14:33:58 -0400 [thread overview]
Message-ID: <ZfiJFj1IO67FR/z4@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20240315095555.2628684-5-xu.yang_2@nxp.com>
On Fri, Mar 15, 2024 at 05:55:52PM +0800, Xu Yang wrote:
> In current driver, the counter will start firstly and then be configured.
> This sequence is not correct for AXI filter events since the correct
> AXI_MASK and AXI_ID are not set yet. Then the results may be inaccurate.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
This one should be bug fix. Can you add fixes tag?
>
> ---
> Changes in v5:
> - new patch
> Changes in v6:
> - no changes
> Changes in v7:
> - no changes
> ---
> drivers/perf/fsl_imx9_ddr_perf.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/perf/fsl_imx9_ddr_perf.c b/drivers/perf/fsl_imx9_ddr_perf.c
> index 5537f4e07852..c99c43b214cb 100644
> --- a/drivers/perf/fsl_imx9_ddr_perf.c
> +++ b/drivers/perf/fsl_imx9_ddr_perf.c
> @@ -523,12 +523,12 @@ static int ddr_perf_event_add(struct perf_event *event, int flags)
> hwc->idx = counter;
> hwc->state |= PERF_HES_STOPPED;
>
> - if (flags & PERF_EF_START)
> - ddr_perf_event_start(event, flags);
> -
> /* read trans, write trans, read beat */
> imx93_ddr_perf_monitor_config(pmu, event_id, counter, cfg1, cfg2);
>
> + if (flags & PERF_EF_START)
> + ddr_perf_event_start(event, flags);
> +
> return 0;
> }
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2024-03-18 18:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 9:55 [PATCH v7 1/8] dt-bindings: perf: fsl-imx-ddr: Add i.MX95 compatible Xu Yang
2024-03-15 9:55 ` [PATCH v7 2/8] perf: imx_perf: add macro definitions for parsing config attr Xu Yang
2024-03-18 16:20 ` Frank Li
2024-03-15 9:55 ` [PATCH v7 3/8] perf: imx_perf: let the driver manage the counter usage rather the user Xu Yang
2024-03-18 16:24 ` Frank Li
2024-03-15 9:55 ` [PATCH v7 4/8] perf: imx_perf: refactor driver for imx93 Xu Yang
2024-03-18 18:30 ` Frank Li
2024-03-22 6:31 ` Xu Yang
2024-03-15 9:55 ` [PATCH v7 5/8] perf: imx_perf: fix counter start and config sequence Xu Yang
2024-03-18 18:33 ` Frank Li [this message]
2024-03-22 6:31 ` Xu Yang
2024-03-15 9:55 ` [PATCH v7 6/8] perf: imx_perf: add support for i.MX95 platform Xu Yang
2024-03-15 9:55 ` [PATCH v7 7/8] perf vendor events arm64:: Add i.MX95 DDR Performance Monitor metrics Xu Yang
2024-03-15 20:25 ` Arnaldo Carvalho de Melo
2024-03-18 6:18 ` [EXT] " Xu Yang
2024-03-18 21:26 ` Arnaldo Carvalho de Melo
2024-03-15 9:55 ` [PATCH v7 8/8] perf vendor events arm64:: Add i.MX93 " Xu Yang
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=ZfiJFj1IO67FR/z4@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=irogers@google.com \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will@kernel.org \
--cc=xu.yang_2@nxp.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