From: Tanmay Jagdale <tanmay@marvell.com> To: <will@kernel.org>, <mark.rutland@arm.com> Cc: <sgoutham@marvell.com>, <bbhushan2@marvell.com>, <lcherian@marvell.com>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, Tanmay Jagdale <tanmay@marvell.com> Subject: [PATCH] perf/marvell_cn10k: Fix tad_pmu_event_init() to check pmu type first Date: Tue, 10 May 2022 15:56:57 +0530 [thread overview] Message-ID: <20220510102657.487539-1-tanmay@marvell.com> (raw) Make sure to check the pmu type first and then check event->attr.disabled. Doing so would avoid reading the disabled attribute of an event that is not handled by TAD PMU. Signed-off-by: Tanmay Jagdale <tanmay@marvell.com> --- drivers/perf/marvell_cn10k_tad_pmu.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/perf/marvell_cn10k_tad_pmu.c b/drivers/perf/marvell_cn10k_tad_pmu.c index ee67305f822d..282d3a071a67 100644 --- a/drivers/perf/marvell_cn10k_tad_pmu.c +++ b/drivers/perf/marvell_cn10k_tad_pmu.c @@ -146,12 +146,12 @@ static int tad_pmu_event_init(struct perf_event *event) { struct tad_pmu *tad_pmu = to_tad_pmu(event->pmu); - if (!event->attr.disabled) - return -EINVAL; - if (event->attr.type != event->pmu->type) return -ENOENT; + if (!event->attr.disabled) + return -EINVAL; + if (event->state != PERF_EVENT_STATE_OFF) return -EINVAL; -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Tanmay Jagdale <tanmay@marvell.com> To: <will@kernel.org>, <mark.rutland@arm.com> Cc: <sgoutham@marvell.com>, <bbhushan2@marvell.com>, <lcherian@marvell.com>, <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, Tanmay Jagdale <tanmay@marvell.com> Subject: [PATCH] perf/marvell_cn10k: Fix tad_pmu_event_init() to check pmu type first Date: Tue, 10 May 2022 15:56:57 +0530 [thread overview] Message-ID: <20220510102657.487539-1-tanmay@marvell.com> (raw) Make sure to check the pmu type first and then check event->attr.disabled. Doing so would avoid reading the disabled attribute of an event that is not handled by TAD PMU. Signed-off-by: Tanmay Jagdale <tanmay@marvell.com> --- drivers/perf/marvell_cn10k_tad_pmu.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/perf/marvell_cn10k_tad_pmu.c b/drivers/perf/marvell_cn10k_tad_pmu.c index ee67305f822d..282d3a071a67 100644 --- a/drivers/perf/marvell_cn10k_tad_pmu.c +++ b/drivers/perf/marvell_cn10k_tad_pmu.c @@ -146,12 +146,12 @@ static int tad_pmu_event_init(struct perf_event *event) { struct tad_pmu *tad_pmu = to_tad_pmu(event->pmu); - if (!event->attr.disabled) - return -EINVAL; - if (event->attr.type != event->pmu->type) return -ENOENT; + if (!event->attr.disabled) + return -EINVAL; + if (event->state != PERF_EVENT_STATE_OFF) return -EINVAL; -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-05-10 10:27 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-10 10:26 Tanmay Jagdale [this message] 2022-05-10 10:26 ` [PATCH] perf/marvell_cn10k: Fix tad_pmu_event_init() to check pmu type first Tanmay Jagdale 2022-05-10 11:33 ` Will Deacon 2022-05-10 11:33 ` Will Deacon
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=20220510102657.487539-1-tanmay@marvell.com \ --to=tanmay@marvell.com \ --cc=bbhushan2@marvell.com \ --cc=lcherian@marvell.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=sgoutham@marvell.com \ --cc=will@kernel.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: linkBe 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.