* [PATCH] drivers/perf: Risc-V: Update platform specific firmware event handling
@ 2023-08-14 4:31 Mayuresh Chitale
2023-08-15 13:14 ` Conor Dooley
2023-08-15 13:19 ` Conor Dooley
0 siblings, 2 replies; 4+ messages in thread
From: Mayuresh Chitale @ 2023-08-14 4:31 UTC (permalink / raw)
To: Atish Patra, Anup Patel
Cc: Mayuresh Chitale, Andrew Jones, Paul Walmsley, Palmer Dabbelt,
Albert Ou, Will Deacon, Mark Rutland, Heiko Stuebner,
Conor Dooley, linux-riscv
SBI specification [1] reserves an event code for platform specific
firmware events. Update the driver to use the new reserved event code
for platform specific firmware events. Also update the raw event parsing
to use bits 63:62 instead of only bit 63 to distinguish between the raw
event types. The platform specific firmware events must be specified in
the perf command as in the below example:
perf stat -e rc000000000000001 <command>
where [63:62] = 0x3 indicates a platform specific firmware event
Link: https://github.com/riscv-non-isa/riscv-sbi-doc/commit/c4bfdf9 [1]
Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
---
arch/riscv/include/asm/sbi.h | 1 +
drivers/perf/riscv_pmu_sbi.c | 29 +++++++++++++++++++++--------
2 files changed, 22 insertions(+), 8 deletions(-)
diff --git a/arch/riscv/include/asm/sbi.h b/arch/riscv/include/asm/sbi.h
index 5b4a1bf5f439..001387354c2e 100644
--- a/arch/riscv/include/asm/sbi.h
+++ b/arch/riscv/include/asm/sbi.h
@@ -138,6 +138,7 @@ union sbi_pmu_ctr_info {
#define RISCV_PMU_RAW_EVENT_MASK GENMASK_ULL(47, 0)
#define RISCV_PMU_RAW_EVENT_IDX 0x20000
+#define RISCV_PLAT_FW_EVENT 0xFFFF
/** General pmu event codes specified in SBI PMU extension */
enum sbi_pmu_hw_generic_events_t {
diff --git a/drivers/perf/riscv_pmu_sbi.c b/drivers/perf/riscv_pmu_sbi.c
index 4163ff517471..f94a3f0a469b 100644
--- a/drivers/perf/riscv_pmu_sbi.c
+++ b/drivers/perf/riscv_pmu_sbi.c
@@ -414,7 +414,6 @@ static int pmu_sbi_event_map(struct perf_event *event, u64 *econfig)
{
u32 type = event->attr.type;
u64 config = event->attr.config;
- int bSoftware;
u64 raw_config_val;
int ret;
@@ -429,18 +428,32 @@ static int pmu_sbi_event_map(struct perf_event *event, u64 *econfig)
break;
case PERF_TYPE_RAW:
/*
- * As per SBI specification, the upper 16 bits must be unused for
- * a raw event. Use the MSB (63b) to distinguish between hardware
- * raw event and firmware events.
+ * As per SBI specification, the upper 16 bits must be unused
+ * for a raw event. Hence bits 63:62 are used to distinguish
+ * between raw events:
+ * 00 - Hardware raw event
+ * 10 - SBI firmware events
+ * 11 - Risc-V platform specific firmware event
*/
- bSoftware = config >> 63;
raw_config_val = config & RISCV_PMU_RAW_EVENT_MASK;
- if (bSoftware) {
+ switch (config >> 62) {
+ case 0:
+ ret = RISCV_PMU_RAW_EVENT_IDX;
+ *econfig = raw_config_val;
+ break;
+ case 2:
ret = (raw_config_val & 0xFFFF) |
(SBI_PMU_EVENT_TYPE_FW << 16);
- } else {
- ret = RISCV_PMU_RAW_EVENT_IDX;
+ break;
+ case 3:
+ /*
+ * For Risc-V platform specific firmware events
+ * Event code - 0xFFFF
+ * Event data - raw event encoding
+ */
+ ret = SBI_PMU_EVENT_TYPE_FW << 16 | RISCV_PLAT_FW_EVENT;
*econfig = raw_config_val;
+ break;
}
break;
default:
--
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] drivers/perf: Risc-V: Update platform specific firmware event handling
2023-08-14 4:31 [PATCH] drivers/perf: Risc-V: Update platform specific firmware event handling Mayuresh Chitale
@ 2023-08-15 13:14 ` Conor Dooley
2023-08-15 13:19 ` Conor Dooley
1 sibling, 0 replies; 4+ messages in thread
From: Conor Dooley @ 2023-08-15 13:14 UTC (permalink / raw)
To: Mayuresh Chitale
Cc: Atish Patra, Anup Patel, Andrew Jones, Paul Walmsley,
Palmer Dabbelt, Albert Ou, Will Deacon, Mark Rutland,
Heiko Stuebner, Conor Dooley, linux-riscv
[-- Attachment #1.1: Type: text/plain, Size: 615 bytes --]
On Mon, Aug 14, 2023 at 10:01:34AM +0530, Mayuresh Chitale wrote:
> + /*
> + * For Risc-V platform specific firmware events
This is a nit, but it my OCD is triggered every time I read it - please
don't invent another style of writing the name of the architecture, both
here and in the commit message. If you respin for some other reason,
could you please change these to one of the established styles?
Thanks,
Conor.
> + * Event code - 0xFFFF
> + * Event data - raw event encoding
> + */
> + ret = SBI_PMU_EVENT_TYPE_FW << 16 | RISCV_PLAT_FW_EVENT;
> *econfig = raw_config_val;
> + break;
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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] drivers/perf: Risc-V: Update platform specific firmware event handling
2023-08-14 4:31 [PATCH] drivers/perf: Risc-V: Update platform specific firmware event handling Mayuresh Chitale
2023-08-15 13:14 ` Conor Dooley
@ 2023-08-15 13:19 ` Conor Dooley
2023-08-16 6:58 ` Atish Patra
1 sibling, 1 reply; 4+ messages in thread
From: Conor Dooley @ 2023-08-15 13:19 UTC (permalink / raw)
To: Mayuresh Chitale
Cc: Atish Patra, Anup Patel, Andrew Jones, Paul Walmsley,
Palmer Dabbelt, Albert Ou, Will Deacon, Mark Rutland,
Heiko Stuebner, Conor Dooley, linux-riscv
[-- Attachment #1.1: Type: text/plain, Size: 937 bytes --]
On Mon, Aug 14, 2023 at 10:01:34AM +0530, Mayuresh Chitale wrote:
> SBI specification [1] reserves an event code for platform specific
> firmware events. Update the driver to use the new reserved event code
> for platform specific firmware events. Also update the raw event parsing
> to use bits 63:62 instead of only bit 63 to distinguish between the raw
> event types. The platform specific firmware events must be specified in
> the perf command as in the below example:
> perf stat -e rc000000000000001 <command>
> where [63:62] = 0x3 indicates a platform specific firmware event
>
> Link: https://github.com/riscv-non-isa/riscv-sbi-doc/commit/c4bfdf9 [1]
> Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
Hmm, another question - is this actually in a frozen version of the SBI
spec? I might've got distracted during the last PRS meeting and be
unaware, but I had it in my head that it was not frozen.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
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] drivers/perf: Risc-V: Update platform specific firmware event handling
2023-08-15 13:19 ` Conor Dooley
@ 2023-08-16 6:58 ` Atish Patra
0 siblings, 0 replies; 4+ messages in thread
From: Atish Patra @ 2023-08-16 6:58 UTC (permalink / raw)
To: Conor Dooley
Cc: Mayuresh Chitale, Anup Patel, Andrew Jones, Paul Walmsley,
Palmer Dabbelt, Albert Ou, Will Deacon, Mark Rutland,
Heiko Stuebner, Conor Dooley, linux-riscv
On Tue, Aug 15, 2023 at 6:19 AM Conor Dooley <conor@kernel.org> wrote:
>
> On Mon, Aug 14, 2023 at 10:01:34AM +0530, Mayuresh Chitale wrote:
> > SBI specification [1] reserves an event code for platform specific
> > firmware events. Update the driver to use the new reserved event code
> > for platform specific firmware events. Also update the raw event parsing
> > to use bits 63:62 instead of only bit 63 to distinguish between the raw
> > event types. The platform specific firmware events must be specified in
> > the perf command as in the below example:
> > perf stat -e rc000000000000001 <command>
> > where [63:62] = 0x3 indicates a platform specific firmware event
> >
> > Link: https://github.com/riscv-non-isa/riscv-sbi-doc/commit/c4bfdf9 [1]
> > Signed-off-by: Mayuresh Chitale <mchitale@ventanamicro.com>
>
> Hmm, another question - is this actually in a frozen version of the SBI
> spec? I might've got distracted during the last PRS meeting and be
> unaware, but I had it in my head that it was not frozen.
Yes. It is not frozen yet. We are in the process of getting all the
RVI approvals to freeze the spec.
--
Regards,
Atish
_______________________________________________
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:[~2023-08-16 6:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-14 4:31 [PATCH] drivers/perf: Risc-V: Update platform specific firmware event handling Mayuresh Chitale
2023-08-15 13:14 ` Conor Dooley
2023-08-15 13:19 ` Conor Dooley
2023-08-16 6:58 ` Atish Patra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox