From: Mark Rutland <mark.rutland@arm.com>
To: "JiaLong.Yang" <jialong.yang@shingroup.cn>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/s390/perf: Register cpumf_pmu with type = PERF_TYPE_RAW
Date: Mon, 4 Mar 2024 09:34:03 +0000 [thread overview]
Message-ID: <ZeWVi6pua5QVqz_y@FVFF77S0Q05N> (raw)
In-Reply-To: <20240304022701.7362-1-jialong.yang@shingroup.cn>
On Mon, Mar 04, 2024 at 10:27:01AM +0800, JiaLong.Yang wrote:
> The struct pmu cpumf_pmu has handled generic events. So it need some
> flags to tell core this thing.
It's not necessary to register as PERF_TYPE_RAW in order to handle raw events,
and PERF_TYPE_RAW is not a flag.
Have you encountered a functional problem, or was this found by inspection?
Mark.
> Signed-off-by: JiaLong.Yang <jialong.yang@shingroup.cn>
> ---
> arch/s390/kernel/perf_cpum_cf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/s390/kernel/perf_cpum_cf.c b/arch/s390/kernel/perf_cpum_cf.c
> index 41ed6e0f0a2a..6ba36cf50091 100644
> --- a/arch/s390/kernel/perf_cpum_cf.c
> +++ b/arch/s390/kernel/perf_cpum_cf.c
> @@ -1213,7 +1213,7 @@ static int __init cpumf_pmu_init(void)
> debug_register_view(cf_dbg, &debug_sprintf_view);
>
> cpumf_pmu.attr_groups = cpumf_cf_event_group();
> - rc = perf_pmu_register(&cpumf_pmu, "cpum_cf", -1);
> + rc = perf_pmu_register(&cpumf_pmu, "cpum_cf", PERF_TYPE_RAW);
> if (rc) {
> pr_err("Registering the cpum_cf PMU failed with rc=%i\n", rc);
> goto out2;
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2024-03-04 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 2:27 [PATCH] arch/s390/perf: Register cpumf_pmu with type = PERF_TYPE_RAW JiaLong.Yang
2024-03-04 9:34 ` Mark Rutland [this message]
2024-03-05 1:43 ` Yang Jialong 杨佳龙
2024-03-05 12:40 ` Mark Rutland
2024-03-05 14:16 ` Jialong 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=ZeWVi6pua5QVqz_y@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jialong.yang@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.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