* [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event
@ 2024-08-31 7:15 Pu Lehui
2024-09-09 2:33 ` Pu Lehui
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Pu Lehui @ 2024-08-31 7:15 UTC (permalink / raw)
To: linux-riscv
Cc: Atish Patra, Anup Patel, Palmer Dabbelt, Björn Töpel,
Pu Lehui
From: Pu Lehui <pulehui@huawei.com>
RISC-V perf driver does not yet support PERF_TYPE_BREAKPOINT. It would
be more appropriate to return -EOPNOTSUPP or -ENOENT for this type in
pmu_sbi_event_map. Considering that other implementations return -ENOENT
for unsupported perf types, let's synchronize this behavior. Due to this
reason, a riscv bpf testcases perf_skip fail. Meanwhile, align that
behavior to the rest of proper place.
Signed-off-by: Pu Lehui <pulehui@huawei.com>
---
drivers/perf/riscv_pmu_legacy.c | 4 ++--
drivers/perf/riscv_pmu_sbi.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/perf/riscv_pmu_legacy.c b/drivers/perf/riscv_pmu_legacy.c
index 04487ad7fba0..93c8e0fdb589 100644
--- a/drivers/perf/riscv_pmu_legacy.c
+++ b/drivers/perf/riscv_pmu_legacy.c
@@ -22,13 +22,13 @@ static int pmu_legacy_ctr_get_idx(struct perf_event *event)
struct perf_event_attr *attr = &event->attr;
if (event->attr.type != PERF_TYPE_HARDWARE)
- return -EOPNOTSUPP;
+ return -ENOENT;
if (attr->config == PERF_COUNT_HW_CPU_CYCLES)
return RISCV_PMU_LEGACY_CYCLE;
else if (attr->config == PERF_COUNT_HW_INSTRUCTIONS)
return RISCV_PMU_LEGACY_INSTRET;
else
- return -EOPNOTSUPP;
+ return -ENOENT;
}
/* For legacy config & counter index are same */
diff --git a/drivers/perf/riscv_pmu_sbi.c b/drivers/perf/riscv_pmu_sbi.c
index 44d3951d009f..169c5157b916 100644
--- a/drivers/perf/riscv_pmu_sbi.c
+++ b/drivers/perf/riscv_pmu_sbi.c
@@ -309,7 +309,7 @@ static void pmu_sbi_check_event(struct sbi_pmu_event_data *edata)
ret.value, 0x1, SBI_PMU_STOP_FLAG_RESET, 0, 0, 0);
} else if (ret.error == SBI_ERR_NOT_SUPPORTED) {
/* This event cannot be monitored by any counter */
- edata->event_idx = -EINVAL;
+ edata->event_idx = -ENOENT;
}
}
@@ -543,7 +543,7 @@ static int pmu_sbi_event_map(struct perf_event *event, u64 *econfig)
}
break;
default:
- ret = -EINVAL;
+ ret = -ENOENT;
break;
}
--
2.34.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event
2024-08-31 7:15 [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event Pu Lehui
@ 2024-09-09 2:33 ` Pu Lehui
2024-09-12 13:48 ` Atish Patra
2024-10-01 11:35 ` patchwork-bot+linux-riscv
2 siblings, 0 replies; 4+ messages in thread
From: Pu Lehui @ 2024-09-09 2:33 UTC (permalink / raw)
To: Atish Patra, linux-riscv
Cc: Atish Patra, Anup Patel, Palmer Dabbelt, Björn Töpel,
Pu Lehui
On 2024/8/31 15:15, Pu Lehui wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> RISC-V perf driver does not yet support PERF_TYPE_BREAKPOINT. It would
> be more appropriate to return -EOPNOTSUPP or -ENOENT for this type in
> pmu_sbi_event_map. Considering that other implementations return -ENOENT
> for unsupported perf types, let's synchronize this behavior. Due to this
> reason, a riscv bpf testcases perf_skip fail. Meanwhile, align that
> behavior to the rest of proper place.
Hi Atish,
Is current modification appropriate? Hope if you have time to review it.
Thanks.
>
> Signed-off-by: Pu Lehui <pulehui@huawei.com>
> ---
> drivers/perf/riscv_pmu_legacy.c | 4 ++--
> drivers/perf/riscv_pmu_sbi.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/perf/riscv_pmu_legacy.c b/drivers/perf/riscv_pmu_legacy.c
> index 04487ad7fba0..93c8e0fdb589 100644
> --- a/drivers/perf/riscv_pmu_legacy.c
> +++ b/drivers/perf/riscv_pmu_legacy.c
> @@ -22,13 +22,13 @@ static int pmu_legacy_ctr_get_idx(struct perf_event *event)
> struct perf_event_attr *attr = &event->attr;
>
> if (event->attr.type != PERF_TYPE_HARDWARE)
> - return -EOPNOTSUPP;
> + return -ENOENT;
> if (attr->config == PERF_COUNT_HW_CPU_CYCLES)
> return RISCV_PMU_LEGACY_CYCLE;
> else if (attr->config == PERF_COUNT_HW_INSTRUCTIONS)
> return RISCV_PMU_LEGACY_INSTRET;
> else
> - return -EOPNOTSUPP;
> + return -ENOENT;
> }
>
> /* For legacy config & counter index are same */
> diff --git a/drivers/perf/riscv_pmu_sbi.c b/drivers/perf/riscv_pmu_sbi.c
> index 44d3951d009f..169c5157b916 100644
> --- a/drivers/perf/riscv_pmu_sbi.c
> +++ b/drivers/perf/riscv_pmu_sbi.c
> @@ -309,7 +309,7 @@ static void pmu_sbi_check_event(struct sbi_pmu_event_data *edata)
> ret.value, 0x1, SBI_PMU_STOP_FLAG_RESET, 0, 0, 0);
> } else if (ret.error == SBI_ERR_NOT_SUPPORTED) {
> /* This event cannot be monitored by any counter */
> - edata->event_idx = -EINVAL;
> + edata->event_idx = -ENOENT;
> }
> }
>
> @@ -543,7 +543,7 @@ static int pmu_sbi_event_map(struct perf_event *event, u64 *econfig)
> }
> break;
> default:
> - ret = -EINVAL;
> + ret = -ENOENT;
> break;
> }
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event
2024-08-31 7:15 [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event Pu Lehui
2024-09-09 2:33 ` Pu Lehui
@ 2024-09-12 13:48 ` Atish Patra
2024-10-01 11:35 ` patchwork-bot+linux-riscv
2 siblings, 0 replies; 4+ messages in thread
From: Atish Patra @ 2024-09-12 13:48 UTC (permalink / raw)
To: Pu Lehui, linux-riscv
Cc: Atish Patra, Anup Patel, Palmer Dabbelt, Björn Töpel,
Pu Lehui
On 8/31/24 12:15 AM, Pu Lehui wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> RISC-V perf driver does not yet support PERF_TYPE_BREAKPOINT. It would
> be more appropriate to return -EOPNOTSUPP or -ENOENT for this type in
> pmu_sbi_event_map. Considering that other implementations return -ENOENT
> for unsupported perf types, let's synchronize this behavior. Due to this
> reason, a riscv bpf testcases perf_skip fail. Meanwhile, align that
> behavior to the rest of proper place.
>
> Signed-off-by: Pu Lehui <pulehui@huawei.com>
> ---
> drivers/perf/riscv_pmu_legacy.c | 4 ++--
> drivers/perf/riscv_pmu_sbi.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/perf/riscv_pmu_legacy.c b/drivers/perf/riscv_pmu_legacy.c
> index 04487ad7fba0..93c8e0fdb589 100644
> --- a/drivers/perf/riscv_pmu_legacy.c
> +++ b/drivers/perf/riscv_pmu_legacy.c
> @@ -22,13 +22,13 @@ static int pmu_legacy_ctr_get_idx(struct perf_event *event)
> struct perf_event_attr *attr = &event->attr;
>
> if (event->attr.type != PERF_TYPE_HARDWARE)
> - return -EOPNOTSUPP;
> + return -ENOENT;
> if (attr->config == PERF_COUNT_HW_CPU_CYCLES)
> return RISCV_PMU_LEGACY_CYCLE;
> else if (attr->config == PERF_COUNT_HW_INSTRUCTIONS)
> return RISCV_PMU_LEGACY_INSTRET;
> else
> - return -EOPNOTSUPP;
> + return -ENOENT;
> }
>
> /* For legacy config & counter index are same */
> diff --git a/drivers/perf/riscv_pmu_sbi.c b/drivers/perf/riscv_pmu_sbi.c
> index 44d3951d009f..169c5157b916 100644
> --- a/drivers/perf/riscv_pmu_sbi.c
> +++ b/drivers/perf/riscv_pmu_sbi.c
> @@ -309,7 +309,7 @@ static void pmu_sbi_check_event(struct sbi_pmu_event_data *edata)
> ret.value, 0x1, SBI_PMU_STOP_FLAG_RESET, 0, 0, 0);
> } else if (ret.error == SBI_ERR_NOT_SUPPORTED) {
> /* This event cannot be monitored by any counter */
> - edata->event_idx = -EINVAL;
> + edata->event_idx = -ENOENT;
> }
> }
>
> @@ -543,7 +543,7 @@ static int pmu_sbi_event_map(struct perf_event *event, u64 *econfig)
> }
> break;
> default:
> - ret = -EINVAL;
> + ret = -ENOENT;
> break;
> }
>
Lgtm. Thanks for aligning the error codes in other places.
Reviewed-by: Atish Patra <atishp@rivosinc.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event
2024-08-31 7:15 [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event Pu Lehui
2024-09-09 2:33 ` Pu Lehui
2024-09-12 13:48 ` Atish Patra
@ 2024-10-01 11:35 ` patchwork-bot+linux-riscv
2 siblings, 0 replies; 4+ messages in thread
From: patchwork-bot+linux-riscv @ 2024-10-01 11:35 UTC (permalink / raw)
To: Pu Lehui; +Cc: linux-riscv, atishp, anup, palmer, bjorn, pulehui
Hello:
This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:
On Sat, 31 Aug 2024 07:15:20 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> RISC-V perf driver does not yet support PERF_TYPE_BREAKPOINT. It would
> be more appropriate to return -EOPNOTSUPP or -ENOENT for this type in
> pmu_sbi_event_map. Considering that other implementations return -ENOENT
> for unsupported perf types, let's synchronize this behavior. Due to this
> reason, a riscv bpf testcases perf_skip fail. Meanwhile, align that
> behavior to the rest of proper place.
>
> [...]
Here is the summary with links:
- [v2] drivers/perf: riscv: Align errno for unsupported perf event
https://git.kernel.org/riscv/c/c625154993d0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-10-01 11:51 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-31 7:15 [PATCH v2] drivers/perf: riscv: Align errno for unsupported perf event Pu Lehui
2024-09-09 2:33 ` Pu Lehui
2024-09-12 13:48 ` Atish Patra
2024-10-01 11:35 ` patchwork-bot+linux-riscv
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox