drivers/perf: CPU PMU driver for Apple M1
Subsystems (5)
v2 cover drivers/perf: CPU PMU driver for Apple M1
The M1 SoC embeds a per-CPU PMU that has a very different programming interface compared to the architected PMUv3 that is normally present on standard implementations.
This small series adds a driver for this HW by leveraging the arm_pmu infrastructure, resulting in a rather simple driver.
Of course, we know next to nothing about the actual events this PMU counts, aside from CPU cycles and instructions. Everything else is undocumented (though as Dougall pointed out, someone could extract the relevant information from a macOS install if they wanted -- I don't).
My hope is that this driver will help people to explore the event space and propose possible interpretations for these events using reproducible test cases.
* From v1 [1]:
- Added a few comments clarifying the event mapping to counters
- Spelling fixes
- Collected Acks from Rob
[1] https://lore.kernel.org/r/[email protected]
Marc Zyngier (8):
dt-bindings: arm-pmu: Document Apple PMU compatible strings
dt-bindings: apple,aic: Add CPU PMU per-cpu pseudo-interrupts irqchip/apple-aic: Add cpumasks for E and P cores irqchip/apple-aic: Wire PMU interrupts irqchip/apple-aic: Move PMU-specific registers to their own include
file
arm64: apple: t8301: Add PMU nodes
drivers/perf: arm_pmu: Handle 47 bit counters drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
.../devicetree/bindings/arm/pmu.yaml | 2 + .../interrupt-controller/apple,aic.yaml | 2 + arch/arm64/boot/dts/apple/t8103.dtsi | 12 + arch/arm64/include/asm/apple_m1_pmu.h | 64 ++ drivers/irqchip/irq-apple-aic.c | 59 +- drivers/perf/Kconfig | 7 + drivers/perf/Makefile | 1 + drivers/perf/apple_m1_cpu_pmu.c | 637 ++++++++++++++++++ drivers/perf/arm_pmu.c | 2 + .../interrupt-controller/apple-aic.h | 2 + include/linux/perf/arm_pmu.h | 2 + 11 files changed, 768 insertions(+), 22 deletions(-) create mode 100644 arch/arm64/include/asm/apple_m1_pmu.h create mode 100644 drivers/perf/apple_m1_cpu_pmu.c
Signature · 1 line
2.30.2
PATCH v2 1/8 dt-bindings: arm-pmu: Document Apple PMU compatible strings
As we are about to add support fur the Apple PMUs, document the compatible strings associated with the two micro-architectures present in the Apple M1.
--- Documentation/devicetree/bindings/arm/pmu.yaml | 2 ++ 1 file changed, 2 insertions(+)
Documentation/devicetree/bindings/arm/pmu.yaml +2 -0
@@ -20,6 +20,8 @@ properties: items: - enum: - apm,potenza-pmu + - apple,firestorm-pmu + - apple,icestorm-pmu - arm,armv8-pmuv3 # Only for s/w models - arm,arm1136-pmu - arm,arm1176-pmu
Signature · 1 line
2.30.2
Re: [PATCH v2 1/8] dt-bindings: arm-pmu: Document Apple PMU compatible strings
Quoted 15 lines · Marc Zyngier
As we are about to add support fur the Apple PMUs, document the compatible strings associated with the two micro-architectures present in the Apple M1.
Acked-by Rob Herring <[email protected]>Signed-off-by Marc Zyngier <[email protected]>--- Documentation/devicetree/bindings/arm/pmu.yaml | 2 ++ 1 file changed, 2 insertions(+)Documentation/devicetree/bindings/arm/pmu.yaml +0
-0
Documentation/devicetree/bindings/arm/pmu.yaml properties: · line 27
Quoted 8 lines
Documentation/devicetree/bindings/arm/pmu.yaml +2
-0@@ -20,6 +20,8 @@ properties: items: - enum: - apm,potenza-pmu + - apple,firestorm-pmu + - apple,icestorm-pmu - arm,armv8-pmuv3 # Only for s/w models - arm,arm1136-pmu - arm,arm1176-pmu
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
PATCH v2 2/8 dt-bindings: apple,aic: Add CPU PMU per-cpu pseudo-interrupts
In reply to Marc ZyngierAdvertise the two pseudo-interrupts that tied to the two PMU flavours present in the Apple M1 SoC.
We choose the expose two different pseudo-interrupts to the OS as the e-core PMU is obviously different from the p-core one, effectively presenting two different devices.
--- .../devicetree/bindings/interrupt-controller/apple,aic.yaml | 2 ++ include/dt-bindings/interrupt-controller/apple-aic.h | 2 ++ 2 files changed, 4 insertions(+)
Documentation/devicetree/bindings/interrupt-controller/apple,aic.yaml +2 -0
@@ -56,6 +56,8 @@ properties: - 1: virtual HV timer - 2: physical guest timer - 3: virtual guest timer + - 4: 'efficient' CPU PMU + - 5: 'performance' CPU PMU The 3rd cell contains the interrupt flags. This is normally IRQ_TYPE_LEVEL_HIGH (4).
include/dt-bindings/interrupt-controller/apple-aic.h +2 -0
@@ -11,5 +11,7 @@#define AIC_TMR_HV_VIRT 1#define AIC_TMR_GUEST_PHYS 2#define AIC_TMR_GUEST_VIRT 3 +#define AIC_CPU_PMU_E 4 +#define AIC_CPU_PMU_P 5#endif
Signature · 1 line
2.30.2
Re: [PATCH v2 2/8] dt-bindings: apple,aic: Add CPU PMU per-cpu pseudo-interrupts
Quoted 33 lines · Marc Zyngier
Advertise the two pseudo-interrupts that tied to the two PMU flavours present in the Apple M1 SoC.
We choose the expose two different pseudo-interrupts to the OS as the e-core PMU is obviously different from the p-core one, effectively presenting two different devices.
Acked-by Rob Herring <[email protected]>Signed-off-by Marc Zyngier <[email protected]>--- .../devicetree/bindings/interrupt-controller/apple,aic.yaml | 2 ++ include/dt-bindings/interrupt-controller/apple-aic.h | 2 ++ 2 files changed, 4 insertions(+)Documentation/devicetree/bindings/interrupt-controller/apple,aic.yaml +2
-0@@ -56,6 +56,8 @@ properties: - 1: virtual HV timer - 2: physical guest timer - 3: virtual guest timer + - 4: 'efficient' CPU PMU + - 5: 'performance' CPU PMU The 3rd cell contains the interrupt flags. This is normally IRQ_TYPE_LEVEL_HIGH (4).include/dt-bindings/interrupt-controller/apple-aic.h +0
-0
include/dt-bindings/interrupt-controller/apple-aic.h line 17
Quoted 7 lines
include/dt-bindings/interrupt-controller/apple-aic.h +2
-0@@ -11,5 +11,7 @@#define AIC_TMR_HV_VIRT 1#define AIC_TMR_GUEST_PHYS 2#define AIC_TMR_GUEST_VIRT 3 +#define AIC_CPU_PMU_E 4 +#define AIC_CPU_PMU_P 5#endif
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
PATCH v2 3/8 irqchip/apple-aic: Add cpumasks for E and P cores
In reply to Marc ZyngierIn order to be able to tell the core IRQ code about the affinity of the PMU interrupt in later patches, compute the cpumasks of the P and E cores at boot time.
This relies on the affinity scheme used by the vendor, which seems to work for the couple of SoCs that are out in the wild.
--- drivers/irqchip/irq-apple-aic.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
drivers/irqchip/irq-apple-aic.c +14 -0
@@ -177,6 +177,8 @@ struct aic_irq_chip {void __iomem *base;struct irq_domain *hw_domain;struct irq_domain *ipi_domain; +struct cpumask ecore_mask; +struct cpumask pcore_mask;int nr_hw;int ipi_hwirq; };
@@ -200,6 +202,11 @@ static void aic_ic_write(struct aic_irq_chip *ic, u32 reg, u32 val)writel_relaxed (val, ic->base + reg); } +static bool __is_pcore (u64 mpidr) +{ +return MPIDR_AFFINITY_LEVEL (mpidr,2 ) ==1 ; +} +/* * IRQ irqchip */
@@ -833,6 +840,13 @@ static int __init aic_of_ic_init(struct device_node *node, struct device_node *preturn -ENODEV ; } +for_each_possible_cpu (i) { +if (__is_pcore (cpu_logical_map (i))) +cpumask_set_cpu (i, &irqc->pcore_mask); +else +cpumask_set_cpu (i, &irqc->ecore_mask); + } +set_handle_irq (aic_handle_irq);set_handle_fiq (aic_handle_fiq);
Signature · 1 line
2.30.2
Mark Rutland
maintainerRe: [PATCH v2 3/8] irqchip/apple-aic: Add cpumasks for E and P cores
Quoted 6 lines · Marc Zyngier
In order to be able to tell the core IRQ code about the affinity of the PMU interrupt in later patches, compute the cpumasks of the P and E cores at boot time.
This relies on the affinity scheme used by the vendor, which seems to work for the couple of SoCs that are out in the wild.
... but may change at any arbitrary point in future?
Can we please put the affinity in the DT, like we do for other SoCs and devices?
I don't think we should treat this HW specially in this regard; we certaintly don't want other folk hard-coding system topology in their irqchip driver, and it should be possible to do something like the ppi-partitions binding, no?
Thanks,
Mark.
Quoted 47 lines
Signed-off-by Marc Zyngier <[email protected]>--- drivers/irqchip/irq-apple-aic.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)drivers/irqchip/irq-apple-aic.c +14
-0@@ -177,6 +177,8 @@ struct aic_irq_chip {void __iomem *base;struct irq_domain *hw_domain;struct irq_domain *ipi_domain; +struct cpumask ecore_mask; +struct cpumask pcore_mask;int nr_hw;int ipi_hwirq; };@@ -200,6 +202,11 @@ static void aic_ic_write(struct aic_irq_chip *ic, u32 reg, u32 val)writel_relaxed (val, ic->base + reg); } +static bool __is_pcore (u64 mpidr) +{ +return MPIDR_AFFINITY_LEVEL (mpidr,2 ) ==1 ; +} +/* * IRQ irqchip */ @@ -833,6 +840,13 @@ static int __init aic_of_ic_init(struct device_node *node, struct device_node *preturn -ENODEV ; } +for_each_possible_cpu (i) { +if (__is_pcore (cpu_logical_map (i))) +cpumask_set_cpu (i, &irqc->pcore_mask); +else +cpumask_set_cpu (i, &irqc->ecore_mask); + } +set_handle_irq (aic_handle_irq);set_handle_fiq (aic_handle_fiq);Signature · 1 line
2.30.2
Re: [PATCH v2 3/8] irqchip/apple-aic: Add cpumasks for E and P cores
Quoted 10 lines · Mark Rutland
Quoted 6 lines · Marc Zyngier
In order to be able to tell the core IRQ code about the affinity of the PMU interrupt in later patches, compute the cpumasks of the P and E cores at boot time.
This relies on the affinity scheme used by the vendor, which seems to work for the couple of SoCs that are out in the wild.
... but may change at any arbitrary point in future?
Crystal balls are in short supply, sorry! ;-)
Quoted 6 lines
Can we please put the affinity in the DT, like we do for other SoCs and devices?
I don't think we should treat this HW specially in this regard; we certaintly don't want other folk hard-coding system topology in their irqchip driver, and it should be possible to do something like the ppi-partitions binding, no?
The PPI partition is totally overkill here. What it deals with is multiple devices sharing a single PPI across the system.
Here, we can invent our own interrupt number, so the sharing is avoided by construction (the joy of not having an interrupt controller the first place!).
I'm happy to stick the affinity in the DT (after all, it is likely that other devices on these systems have the same requirements) and have it consumed by the irqchip driver. I only need to find a way that doesn't completely invalidate the existing binding...
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Re: [PATCH v2 3/8] irqchip/apple-aic: Add cpumasks for E and P cores
Quoted 8 lines · Marc Zyngier
Quoted 6 lines · Mark Rutland
Quoted 4 lines · Marc Zyngier
In order to be able to tell the core IRQ code about the affinity of the PMU interrupt in later patches, compute the cpumasks of the P and E cores at boot time.
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
This relies on the affinity scheme used by the vendor, which seems to work for the couple of SoCs that are out in the wild.
... but may change at any arbitrary point in future?
Crystal balls are in short supply, sorry! ;-)
Considering Apple seem to rely on this all over the place, I think they probably won't be changing the meaning of Aff2 at least until they decide to come up with SoCs that have 3 types of cores, or something like that :)
But yeah, ultimately this is a guess.
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Re: [PATCH v2 3/8] irqchip/apple-aic: Add cpumasks for E and P cores
In reply to Marc ZyngierQuoted 42 lines · Marc Zyngier
In order to be able to tell the core IRQ code about the affinity of the PMU interrupt in later patches, compute the cpumasks of the P and E cores at boot time.
This relies on the affinity scheme used by the vendor, which seems to work for the couple of SoCs that are out in the wild.
Signed-off-by Marc Zyngier <[email protected]>--- drivers/irqchip/irq-apple-aic.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)drivers/irqchip/irq-apple-aic.c +7
-0@@ -177,6 +177,8 @@ struct aic_irq_chip {void __iomem *base;struct irq_domain *hw_domain;struct irq_domain *ipi_domain; +struct cpumask ecore_mask; +struct cpumask pcore_mask;int nr_hw;int ipi_hwirq; };@@ -200,6 +202,11 @@ static void aic_ic_write(struct aic_irq_chip *ic, u32 reg, u32 val)writel_relaxed (val, ic->base + reg); } +static bool __is_pcore (u64 mpidr) +{ +return MPIDR_AFFINITY_LEVEL (mpidr,2 ) ==1 ; +} +/* * IRQ irqchip */ @@ -833,6 +840,13 @@ static int __init aic_of_ic_init(struct device_node *node, struct device_node *preturn -ENODEV ; }
drivers/irqchip/irq-apple-aic.c static int __init aic_of_ic_init(struct device_node *node, struct device_node *p · line 852
Quoted 10 lines
drivers/irqchip/irq-apple-aic.c +7
-0+for_each_possible_cpu (i) { +if (__is_pcore (cpu_logical_map (i))) +cpumask_set_cpu (i, &irqc->pcore_mask); +else +cpumask_set_cpu (i, &irqc->ecore_mask); + } +set_handle_irq (aic_handle_irq);set_handle_fiq (aic_handle_fiq);
I'm okay with this approach, but if we want to be more explicit about the affinities, maybe something like apple,pmu-irq-index in the CPU nodes? Then we can either start at a higher FIQ offset for these (in case we need to add more FIQs in the future), or just make up a new AIC_PMU top level interrupt type and start at 0.
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
Re: [PATCH v2 3/8] irqchip/apple-aic: Add cpumasks for E and P cores
Quoted 49 lines · Hector Martin
Quoted 47 lines · Marc Zyngier
In order to be able to tell the core IRQ code about the affinity of the PMU interrupt in later patches, compute the cpumasks of the P and E cores at boot time.
This relies on the affinity scheme used by the vendor, which seems to work for the couple of SoCs that are out in the wild.
Signed-off-by Marc Zyngier <[email protected]>--- drivers/irqchip/irq-apple-aic.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)drivers/irqchip/irq-apple-aic.c +12
-0@@ -177,6 +177,8 @@ struct aic_irq_chip {void __iomem *base;struct irq_domain *hw_domain;struct irq_domain *ipi_domain; +struct cpumask ecore_mask; +struct cpumask pcore_mask;int nr_hw;int ipi_hwirq; };@@ -200,6 +202,11 @@ static void aic_ic_write(struct aic_irq_chip *ic, u32 reg, u32 val)writel_relaxed (val, ic->base + reg); } +static bool __is_pcore(u64 mpidr) +{ +return MPIDR_AFFINITY_LEVEL (mpidr,2 ) ==1 ; +} +/* * IRQ irqchip */ @@ -833,6 +840,13 @@ static int __init aic_of_ic_init(struct device_node *node, struct device_node *preturn -ENODEV ; } + for_each_possible_cpu(i) { +if (__is_pcore (cpu_logical_map (i))) +cpumask_set_cpu (i, &irqc->pcore_mask); +else +cpumask_set_cpu (i, &irqc->ecore_mask); + } +set_handle_irq (aic_handle_irq);
Quoted 8 lines
drivers/irqchip/irq-apple-aic.c static int __init aic_of_ic_init(struct device_node *node, struct device_node *p · line 852
Quoted 2 lines
drivers/irqchip/irq-apple-aic.c +0
-0set_handle_fiq (aic_handle_fiq);I'm okay with this approach, but if we want to be more explicit about the affinities, maybe something like apple,pmu-irq-index in the CPU nodes? Then we can either start at a higher FIQ offset for these (in case we need to add more FIQs in the future), or just make up a new
AIC_PMUtop level interrupt type and start at 0.
I'm actually worried that we'll need more of these "asymmetric FIQs" in the future, and that the PMU-specific hack won't scale.
Do you know of any other per-CPU device that could differ between small and big cores? This would certainly help guiding my implementation between a device specific hack (the PMU irq index) or something more generic (interrupt specifier containing the affinity and following the AICv2 scheme).
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
PATCH v2 4/8 irqchip/apple-aic: Wire PMU interrupts
In reply to Marc ZyngierAdd the necessary code to configure and P and E-core PMU interrupts with their respective affinities. When such an interrupt fires, map it onto the right pseudo-interrupt.
--- drivers/irqchip/irq-apple-aic.c | 34 +++++++++++++++++++++------------ 1 file changed, 22 insertions(+), 12 deletions(-)
drivers/irqchip/irq-apple-aic.c +22 -12
@@ -155,7 +155,7 @@#define SYS_IMP_APL_UPMSR_EL1 sys_reg(3, 7, 15, 6, 4)#define UPMSR_IACT BIT(0) -#define AIC_NR_FIQ 4 +#define AIC_NR_FIQ 6#define AIC_NR_SWIPI 32/*
@@ -207,6 +207,11 @@ static bool __is_pcore(u64 mpidr)return MPIDR_AFFINITY_LEVEL (mpidr,2 ) ==1 ; } +static bool is_pcore (void ) +{ +return __is_pcore (read_cpuid_mpidr ()); +} +/* * IRQ irqchip */
@@ -420,16 +425,10 @@ static void __exception_irq_entry aic_handle_fiq(struct pt_regs *regs) aic_irqc->nr_hw + AIC_TMR_EL02_VIRT); } -if ((read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ) & (PMCR0_IMODE |PMCR0_IACT )) == - (FIELD_PREP (PMCR0_IMODE ,PMCR0_IMODE_FIQ ) |PMCR0_IACT )) { -/* -* Not supported yet, let's figure out how to handle this when -* we implement these proprietary performance counters. For now, -* just mask it and move on. -*/ -pr_err_ratelimited ("PMC FIQ fired. Masking.\n" ); -sysreg_clear_set_s (SYS_IMP_APL_PMCR0_EL1 ,PMCR0_IMODE |PMCR0_IACT , -FIELD_PREP (PMCR0_IMODE ,PMCR0_IMODE_OFF )); +if (read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ) &PMCR0_IACT ) { +int irq =is_pcore () ?AIC_CPU_PMU_P :AIC_CPU_PMU_E ; +generic_handle_domain_irq (aic_irqc->hw_domain, + aic_irqc->nr_hw + irq); } if (FIELD_GET(UPMCR0_IMODE, read_sysreg_s(SYS_IMP_APL_UPMCR0_EL1)) == UPMCR0_IMODE_FIQ &&
@@ -469,7 +468,18 @@ static int aic_irq_domain_map(struct irq_domain *id, unsigned int irq, handle_fasteoi_irq, NULL, NULL);irqd_set_single_target (irq_desc_get_irq_data (irq_to_desc (irq))); }else { -irq_set_percpu_devid (irq); +switch (hw - ic->nr_hw) { +case AIC_CPU_PMU_P : +irq_set_percpu_devid_partition (irq, &ic->pcore_mask); +break ; +case AIC_CPU_PMU_E : +irq_set_percpu_devid_partition (irq, &ic->ecore_mask); +break ; +default : +irq_set_percpu_devid (irq); +break ; + } +irq_domain_set_info (id, irq, hw, &fiq_chip, id->host_data, handle_percpu_devid_irq,NULL ,NULL ); }
Signature · 1 line
2.30.2
Re: [PATCH v2 4/8] irqchip/apple-aic: Wire PMU interrupts
Quoted 66 lines · Marc Zyngier
Add the necessary code to configure and P and E-core PMU interrupts with their respective affinities. When such an interrupt fires, map it onto the right pseudo-interrupt.
Signed-off-by Marc Zyngier <[email protected]>--- drivers/irqchip/irq-apple-aic.c | 34 +++++++++++++++++++++------------ 1 file changed, 22 insertions(+), 12 deletions(-)drivers/irqchip/irq-apple-aic.c +15
-12@@ -155,7 +155,7 @@#define SYS_IMP_APL_UPMSR_EL1 sys_reg(3, 7, 15, 6, 4)#define UPMSR_IACT BIT(0) -#define AIC_NR_FIQ 4 +#define AIC_NR_FIQ 6#define AIC_NR_SWIPI 32/* @@ -207,6 +207,11 @@ static bool __is_pcore(u64 mpidr)return MPIDR_AFFINITY_LEVEL (mpidr,2 ) ==1 ; } +static bool is_pcore (void ) +{ +return __is_pcore (read_cpuid_mpidr ()); +} +/* * IRQ irqchip */ @@ -420,16 +425,10 @@ static void __exception_irq_entry aic_handle_fiq(struct pt_regs *regs) aic_irqc->nr_hw + AIC_TMR_EL02_VIRT); } -if ((read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ) & (PMCR0_IMODE |PMCR0_IACT )) == - (FIELD_PREP (PMCR0_IMODE ,PMCR0_IMODE_FIQ ) |PMCR0_IACT )) { -/* -* Not supported yet, let's figure out how to handle this when -* we implement these proprietary performance counters. For now, -* just mask it and move on. -*/ -pr_err_ratelimited ("PMC FIQ fired. Masking.\n" ); -sysreg_clear_set_s (SYS_IMP_APL_PMCR0_EL1 ,PMCR0_IMODE |PMCR0_IACT , -FIELD_PREP (PMCR0_IMODE ,PMCR0_IMODE_OFF )); +if (read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ) &PMCR0_IACT ) { +int irq =is_pcore () ?AIC_CPU_PMU_P :AIC_CPU_PMU_E ; +generic_handle_domain_irq (aic_irqc->hw_domain, + aic_irqc->nr_hw + irq); } if (FIELD_GET(UPMCR0_IMODE, read_sysreg_s(SYS_IMP_APL_UPMCR0_EL1)) == UPMCR0_IMODE_FIQ &&@@ -469,7 +468,18 @@ static int aic_irq_domain_map(struct irq_domain *id, unsigned int irq, handle_fasteoi_irq, NULL, NULL);irqd_set_single_target (irq_desc_get_irq_data (irq_to_desc (irq))); }else { -irq_set_percpu_devid (irq); +switch (hw - ic->nr_hw) { +case AIC_CPU_PMU_P : +irq_set_percpu_devid_partition (irq, &ic->pcore_mask); +break ; +case AIC_CPU_PMU_E :
drivers/irqchip/irq-apple-aic.c static int aic_irq_domain_map(struct irq_domain *id, unsigned int irq, · line 485
Quoted 10 lines
drivers/irqchip/irq-apple-aic.c +7
-0+irq_set_percpu_devid_partition (irq, &ic->ecore_mask); +break ; +default : +irq_set_percpu_devid (irq); +break ; + } +irq_domain_set_info (id, irq, hw, &fiq_chip, id->host_data, handle_percpu_devid_irq,NULL ,NULL ); }
I still find this idea that we need to split the IRQs virtually quite bizarre, but if that's how bit.LITTLE systems do it...
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
PATCH v2 5/8 irqchip/apple-aic: Move PMU-specific registers to their own include file
In reply to Marc ZyngierAs we are about to have a PMU driver, move the PMU bits from the AIC driver into a common include file.
--- arch/arm64/include/asm/apple_m1_pmu.h | 19 +++++++++++++++++++ drivers/irqchip/irq-apple-aic.c | 11 +---------- 2 files changed, 20 insertions(+), 10 deletions(-) create mode 100644 arch/arm64/include/asm/apple_m1_pmu.h
arch/arm64/include/asm/apple_m1_pmu.h new file +19 -0
@@ -0,0 +1,19 @@ +// SPDX-License-Identifier: GPL-2.0 + +#ifndef __ASM_APPLE_M1_PMU_h +#define __ASM_APPLE_M1_PMU_h + +#include <linux/bits.h> +#include <asm/sysreg.h> + +/* Core PMC control register */ +#define SYS_IMP_APL_PMCR0_EL1 sys_reg(3, 1, 15, 0, 0) +#define PMCR0_IMODE GENMASK(10, 8) +#define PMCR0_IMODE_OFF 0 +#define PMCR0_IMODE_PMI 1 +#define PMCR0_IMODE_AIC 2 +#define PMCR0_IMODE_HALT 3 +#define PMCR0_IMODE_FIQ 4 +#define PMCR0_IACT BIT(11) + +#endif /* __ASM_APPLE_M1_PMU_h */
drivers/irqchip/irq-apple-aic.c +1 -10
@@ -55,6 +55,7 @@#include <linux/limits.h> #include <linux/of_address.h> #include <linux/slab.h> +#include <asm/apple_m1_pmu.h> #include <asm/exception.h> #include <asm/sysreg.h> #include <asm/virt.h>
@@ -109,16 +110,6 @@* Note: sysreg-based IPIs are not supported yet. */ -/* Core PMC control register */ -#define SYS_IMP_APL_PMCR0_EL1 sys_reg(3, 1, 15, 0, 0) -#define PMCR0_IMODE GENMASK(10, 8) -#define PMCR0_IMODE_OFF 0 -#define PMCR0_IMODE_PMI 1 -#define PMCR0_IMODE_AIC 2 -#define PMCR0_IMODE_HALT 3 -#define PMCR0_IMODE_FIQ 4 -#define PMCR0_IACT BIT(11) -/* IPI request registers */ #define SYS_IMP_APL_IPI_RR_LOCAL_EL1 sys_reg(3, 5, 15, 0, 0)#define SYS_IMP_APL_IPI_RR_GLOBAL_EL1 sys_reg(3, 5, 15, 0, 1)
Signature · 1 line
2.30.2
Re: [PATCH v2 5/8] irqchip/apple-aic: Move PMU-specific registers to their own include file
Quoted 55 lines · Marc Zyngier
As we are about to have a PMU driver, move the PMU bits from the AIC driver into a common include file.
Signed-off-by Marc Zyngier <[email protected]>--- arch/arm64/include/asm/apple_m1_pmu.h | 19 +++++++++++++++++++ drivers/irqchip/irq-apple-aic.c | 11 +---------- 2 files changed, 20 insertions(+), 10 deletions(-)create mode 100644
arch/arm64/include/asm/apple_m1_pmu.harch/arm64/include/asm/apple_m1_pmu.h new file +19
-0@@ -0,0 +1,19 @@ +// SPDX-License-Identifier: GPL-2.0 + +#ifndef __ASM_APPLE_M1_PMU_h +#define __ASM_APPLE_M1_PMU_h + +#include <linux/bits.h> +#include <asm/sysreg.h> + +/* Core PMC control register */ +#define SYS_IMP_APL_PMCR0_EL1 sys_reg(3, 1, 15, 0, 0) +#define PMCR0_IMODE GENMASK(10, 8) +#define PMCR0_IMODE_OFF 0 +#define PMCR0_IMODE_PMI 1 +#define PMCR0_IMODE_AIC 2 +#define PMCR0_IMODE_HALT 3 +#define PMCR0_IMODE_FIQ 4 +#define PMCR0_IACT BIT(11) + +#endif /* __ASM_APPLE_M1_PMU_h */ drivers/irqchip/irq-apple-aic.c +1
-3@@ -55,6 +55,7 @@#include <linux/limits.h> #include <linux/of_address.h> #include <linux/slab.h> +#include <asm/apple_m1_pmu.h> #include <asm/exception.h> #include <asm/sysreg.h> #include <asm/virt.h> @@ -109,16 +110,6 @@* Note: sysreg-based IPIs are not supported yet. */ -/* Core PMC control register */ -#define SYS_IMP_APL_PMCR0_EL1 sys_reg(3, 1, 15, 0, 0) -#define PMCR0_IMODE GENMASK(10, 8)
drivers/irqchip/irq-apple-aic.c line 115
Quoted 10 lines
drivers/irqchip/irq-apple-aic.c +0
-7-#define PMCR0_IMODE_OFF 0 -#define PMCR0_IMODE_PMI 1 -#define PMCR0_IMODE_AIC 2 -#define PMCR0_IMODE_HALT 3 -#define PMCR0_IMODE_FIQ 4 -#define PMCR0_IACT BIT(11) -/* IPI request registers */ #define SYS_IMP_APL_IPI_RR_LOCAL_EL1 sys_reg(3, 5, 15, 0, 0)#define SYS_IMP_APL_IPI_RR_GLOBAL_EL1 sys_reg(3, 5, 15, 0, 1)
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
PATCH v2 6/8 arm64: apple: t8301: Add PMU nodes
In reply to Marc ZyngierAdvertise the two PMU nodes for the t8103 SoC.
--- arch/arm64/boot/dts/apple/t8103.dtsi | 12 ++++++++++++ 1 file changed, 12 insertions(+)
arch/arm64/boot/dts/apple/t8103.dtsi +12 -0
@@ -96,6 +96,18 @@ timer { <AIC_FIQ AIC_TMR_HV_VIRT IRQ_TYPE_LEVEL_HIGH>; }; + pmu-e { + compatible = "apple,icestorm-pmu"; + interrupt-parent = <&aic>; + interrupts = <AIC_FIQ AIC_CPU_PMU_E IRQ_TYPE_LEVEL_HIGH>; + }; + + pmu-p { + compatible = "apple,firestorm-pmu"; + interrupt-parent = <&aic>; + interrupts = <AIC_FIQ AIC_CPU_PMU_P IRQ_TYPE_LEVEL_HIGH>; + }; + clk24: clock-24m { compatible = "fixed-clock"; #clock-cells = <0>;
Signature · 1 line
2.30.2
Re: [PATCH v2 6/8] arm64: apple: t8301: Add PMU nodes
Quoted 21 lines · Marc Zyngier
Advertise the two PMU nodes for the t8103 SoC.
Signed-off-by Marc Zyngier <[email protected]>--- arch/arm64/boot/dts/apple/t8103.dtsi | 12 ++++++++++++ 1 file changed, 12 insertions(+)arch/arm64/boot/dts/apple/t8103.dtsi +5
-0@@ -96,6 +96,18 @@ timer { <AIC_FIQ AIC_TMR_HV_VIRT IRQ_TYPE_LEVEL_HIGH>; }; + pmu-e { + compatible = "apple,icestorm-pmu"; + interrupt-parent = <&aic>; + interrupts = <AIC_FIQ AIC_CPU_PMU_E IRQ_TYPE_LEVEL_HIGH>; + };
arch/arm64/boot/dts/apple/t8103.dtsi timer { · line 113
Quoted 10 lines
arch/arm64/boot/dts/apple/t8103.dtsi +7
-0+ + pmu-p { + compatible = "apple,firestorm-pmu"; + interrupt-parent = <&aic>; + interrupts = <AIC_FIQ AIC_CPU_PMU_P IRQ_TYPE_LEVEL_HIGH>; + }; + clk24: clock-24m { compatible = "fixed-clock"; #clock-cells = <0>;
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
PATCH v2 7/8 drivers/perf: arm_pmu: Handle 47 bit counters
In reply to Marc ZyngierThe current ARM PMU framework can only deal with 32 or 64bit counters. Teach it about a 47bit flavour.
Yes, this is odd.
--- drivers/perf/arm_pmu.c | 2 ++ include/linux/perf/arm_pmu.h | 2 ++ 2 files changed, 4 insertions(+)
drivers/perf/arm_pmu.c +2 -0
@@ -109,6 +109,8 @@ static inline u64 arm_pmu_event_max_period(struct perf_event *event) {if (event->hw.flags &ARMPMU_EVT_64BIT )return GENMASK_ULL (63 ,0 ); +else if (event->hw.flags &ARMPMU_EVT_47BIT ) +return GENMASK_ULL (46 ,0 );else return GENMASK_ULL (31 ,0 ); }
include/linux/perf/arm_pmu.h +2 -0
@@ -26,6 +26,8 @@*/ /* Event uses a 64bit counter */ #define ARMPMU_EVT_64BIT 1 +/* Event uses a 47bit counter */ +#define ARMPMU_EVT_47BIT 2#define HW_OP_UNSUPPORTED 0xFFFF#define C (_x) PERF_COUNT_HW_CACHE_##_x
Signature · 1 line
2.30.2
Re: [PATCH v2 7/8] drivers/perf: arm_pmu: Handle 47 bit counters
Quoted 30 lines · Marc Zyngier
The current ARM PMU framework can only deal with 32 or 64bit counters. Teach it about a 47bit flavour.
Yes, this is odd.
Signed-off-by Marc Zyngier <[email protected]>--- drivers/perf/arm_pmu.c | 2 ++ include/linux/perf/arm_pmu.h | 2 ++ 2 files changed, 4 insertions(+)drivers/perf/arm_pmu.c +2
-0@@ -109,6 +109,8 @@ static inline u64 arm_pmu_event_max_period(struct perf_event *event) {if (event->hw.flags &ARMPMU_EVT_64BIT )return GENMASK_ULL (63 ,0 ); +else if (event->hw.flags &ARMPMU_EVT_47BIT ) +return GENMASK_ULL (46 ,0 );else return GENMASK_ULL (31 ,0 ); }include/linux/perf/arm_pmu.h +0
-0
include/linux/perf/arm_pmu.h line 33
Quoted 8 lines
include/linux/perf/arm_pmu.h +2
-0@@ -26,6 +26,8 @@*/ /* Event uses a 64bit counter */ #define ARMPMU_EVT_64BIT 1 +/* Event uses a 47bit counter */ +#define ARMPMU_EVT_47BIT 2#define HW_OP_UNSUPPORTED 0xFFFF#define C (_x) PERF_COUNT_HW_CACHE_##_x
Signature · 2 lines
Hector Martin ([email protected]) Public Key: https://mrcn.st/pub
PATCH v2 8/8 drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
In reply to Marc ZyngierAdd a new, weird and wonderful driver for the equally weird Apple PMU HW. Although the PMU itself is functional, we don't know much about the events yet, so this can be considered as yet another random number generator...
Nonetheless, it can reliably count at least cycles and instructions in the usually wonky big-little way. For anything else, it of course supports raw event numbers.
--- arch/arm64/include/asm/apple_m1_pmu.h | 45 ++ drivers/perf/Kconfig | 7 + drivers/perf/Makefile | 1 + drivers/perf/apple_m1_cpu_pmu.c | 637 ++++++++++++++++++++++++++ 4 files changed, 690 insertions(+) create mode 100644 drivers/perf/apple_m1_cpu_pmu.c
arch/arm64/include/asm/apple_m1_pmu.h +45 -0
@@ -6,8 +6,21 @@#include <linux/bits.h> #include <asm/sysreg.h> +/* Counters */ +#define SYS_IMP_APL_PMC0_EL1 sys_reg(3, 2, 15, 0, 0) +#define SYS_IMP_APL_PMC1_EL1 sys_reg(3, 2, 15, 1, 0) +#define SYS_IMP_APL_PMC2_EL1 sys_reg(3, 2, 15, 2, 0) +#define SYS_IMP_APL_PMC3_EL1 sys_reg(3, 2, 15, 3, 0) +#define SYS_IMP_APL_PMC4_EL1 sys_reg(3, 2, 15, 4, 0) +#define SYS_IMP_APL_PMC5_EL1 sys_reg(3, 2, 15, 5, 0) +#define SYS_IMP_APL_PMC6_EL1 sys_reg(3, 2, 15, 6, 0) +#define SYS_IMP_APL_PMC7_EL1 sys_reg(3, 2, 15, 7, 0) +#define SYS_IMP_APL_PMC8_EL1 sys_reg(3, 2, 15, 9, 0) +#define SYS_IMP_APL_PMC9_EL1 sys_reg(3, 2, 15, 10, 0) +/* Core PMC control register */ #define SYS_IMP_APL_PMCR0_EL1 sys_reg(3, 1, 15, 0, 0) +#define PMCR0_CNT_ENABLE_0_7 GENMASK(7, 0)#define PMCR0_IMODE GENMASK(10, 8)#define PMCR0_IMODE_OFF 0#define PMCR0_IMODE_PMI 1
@@ -15,5 +28,37 @@#define PMCR0_IMODE_HALT 3#define PMCR0_IMODE_FIQ 4#define PMCR0_IACT BIT(11) +#define PMCR0_PMI_ENABLE_0_7 GENMASK(19, 12) +#define PMCR0_STOP_CNT_ON_PMI BIT(20) +#define PMCR0_CNT_GLOB_L2C_EVT BIT(21) +#define PMCR0_DEFER_PMI_TO_ERET BIT(22) +#define PMCR0_ALLOW_CNT_EN_EL0 BIT(30) +#define PMCR0_CNT_ENABLE_8_9 GENMASK(33, 32) +#define PMCR0_PMI_ENABLE_8_9 GENMASK(45, 44) + +#define SYS_IMP_APL_PMCR1_EL1 sys_reg(3, 1, 15, 1, 0) +#define PMCR1_COUNT_A64_EL0_0_7 GENMASK(15, 8) +#define PMCR1_COUNT_A64_EL1_0_7 GENMASK(23, 16) +#define PMCR1_COUNT_A64_EL0_8_9 GENMASK(41, 40) +#define PMCR1_COUNT_A64_EL1_8_9 GENMASK(49, 48) + +#define SYS_IMP_APL_PMCR2_EL1 sys_reg(3, 1, 15, 2, 0) +#define SYS_IMP_APL_PMCR3_EL1 sys_reg(3, 1, 15, 3, 0) +#define SYS_IMP_APL_PMCR4_EL1 sys_reg(3, 1, 15, 4, 0) + +#define SYS_IMP_APL_PMESR0_EL1 sys_reg(3, 1, 15, 5, 0) +#define PMESR0_EVT_CNT_2 GENMASK(7, 0) +#define PMESR0_EVT_CNT_3 GENMASK(15, 8) +#define PMESR0_EVT_CNT_4 GENMASK(23, 16) +#define PMESR0_EVT_CNT_5 GENMASK(31, 24) + +#define SYS_IMP_APL_PMESR1_EL1 sys_reg(3, 1, 15, 6, 0) +#define PMESR1_EVT_CNT_6 GENMASK(7, 0) +#define PMESR1_EVT_CNT_7 GENMASK(15, 8) +#define PMESR1_EVT_CNT_8 GENMASK(23, 16) +#define PMESR1_EVT_CNT_9 GENMASK(31, 24) + +#define SYS_IMP_APL_PMSR_EL1 sys_reg(3, 1, 15, 13, 0) +#define PMSR_OVERFLOW GENMASK(9, 0)#endif /* __ASM_APPLE_M1_PMU_h */
drivers/perf/Kconfig +7 -0
@@ -139,6 +139,13 @@ config ARM_DMC620_PMU Support for PMU events monitoring on the ARM DMC-620 memory controller. +config APPLE_M1_CPU_PMU + bool "Apple M1 CPU PMU support" + depends on ARM_PMU && ARCH_APPLE + help + Provides support for the non-architectural CPU PMUs present on + the Apple M1 SoCs and derivatives. + source "drivers/perf/hisilicon/Kconfig" endmenu
drivers/perf/Makefile +1 -0
@@ -14,3 +14,4 @@ obj-$(CONFIG_THUNDERX2_PMU) += thunderx2_pmu.o obj-$(CONFIG_XGENE_PMU) += xgene_pmu.o obj-$(CONFIG_ARM_SPE_PMU) += arm_spe_pmu.o obj-$(CONFIG_ARM_DMC620_PMU) += arm_dmc620_pmu.o +obj-$(CONFIG_APPLE_M1_CPU_PMU) += apple_m1_cpu_pmu.o
drivers/perf/apple_m1_cpu_pmu.c new file +637 -0
637 lines not on this page · raw message
Signature · 1 line
2.30.2
Mark Rutland
maintainerRe: [PATCH v2 8/8] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
Quoted 4 lines · Marc Zyngier
Add a new, weird and wonderful driver for the equally weird Apple PMU HW. Although the PMU itself is functional, we don't know much about the events yet, so this can be considered as yet another random number generator...
It's really frustrating that Apple built this rather than the architected PMU, because we've generally pushed back on IMPLEMENTATION DEFINED junk in this area, and supporting this makes it harder to push back on other vendors going the same route, which I'm not keen on. That, and the usual state of IMP-DEF stuff making this stupidly painful to reason about.
I can see that we can get this working bare-metal with DT, but I really don't want to try to support this in other cases (e.g. in a VM, potentially with ACPI), or this IMP-DEFness is going to spread more throughout the arm_pmu code.
How does this interact with PMU emulation for a KVM guest?
I have a bunch of comments and questions below.
[...]
drivers/perf/apple_m1_cpu_pmu.c line 28
Quoted 4 lines
drivers/perf/apple_m1_cpu_pmu.c new file +4
-0+#define ANY_BUT_0_1 GENMASK(9, 2) +#define ONLY_2_TO_7 GENMASK(7, 2) +#define ONLY_2_4_6 (BIT(2) | BIT(4) | BIT(6)) +#define ONLY_5_6_7 GENMASK(7, 5)
For clarity/consistency it might be better to use separate BIT()s for ONLY_5_6_7 too.
Quoted 93 lines
drivers/perf/apple_m1_cpu_pmu.c new file +93
-0+/* +* Description of the events we actually know about, as well as those with +* a specific counter affinity. Yes, this is a grand total of two known +* counters, and the rest is anybody's guess. +* +* Not all counters can count all events. Counters #0 and #1 are wired to +* count cycles and instructions respectively, and some events have +* bizarre mappings (every other counter, or even *one* counter). These +* restrictions equally apply to both P and E cores. +* +* It is worth noting that the PMUs attached to P and E cores are likely +* to be different because the underlying uarches are different. At the +* moment, we don't really need to distinguish between the two because we +* know next to nothing about the events themselves, and we already have +* per cpu-type PMU abstractions. +* +* If we eventually find out that the events are different across +* implementations, we'll have to introduce per cpu-type tables. +*/ +enum m1_pmu_events { +M1_PMU_PERFCTR_UNKNOWN_01 =0x01 , +M1_PMU_PERFCTR_CPU_CYCLES =0x02 , +M1_PMU_PERFCTR_INSTRUCTIONS =0x8c , + M1_PMU_PERFCTR_UNKNOWN_8d =0x8d , + M1_PMU_PERFCTR_UNKNOWN_8e =0x8e , + M1_PMU_PERFCTR_UNKNOWN_8f =0x8f , +M1_PMU_PERFCTR_UNKNOWN_90 =0x90 , +M1_PMU_PERFCTR_UNKNOWN_93 =0x93 , +M1_PMU_PERFCTR_UNKNOWN_94 =0x94 , +M1_PMU_PERFCTR_UNKNOWN_95 =0x95 , +M1_PMU_PERFCTR_UNKNOWN_96 =0x96 , +M1_PMU_PERFCTR_UNKNOWN_97 =0x97 , +M1_PMU_PERFCTR_UNKNOWN_98 =0x98 , +M1_PMU_PERFCTR_UNKNOWN_99 =0x99 , + M1_PMU_PERFCTR_UNKNOWN_9a =0x9a , + M1_PMU_PERFCTR_UNKNOWN_9b =0x9b , + M1_PMU_PERFCTR_UNKNOWN_9c =0x9c , + M1_PMU_PERFCTR_UNKNOWN_9f =0x9f , + M1_PMU_PERFCTR_UNKNOWN_bf =0xbf , + M1_PMU_PERFCTR_UNKNOWN_c0 =0xc0 , + M1_PMU_PERFCTR_UNKNOWN_c1 =0xc1 , + M1_PMU_PERFCTR_UNKNOWN_c4 =0xc4 , + M1_PMU_PERFCTR_UNKNOWN_c5 =0xc5 , + M1_PMU_PERFCTR_UNKNOWN_c6 =0xc6 , + M1_PMU_PERFCTR_UNKNOWN_c8 =0xc8 , + M1_PMU_PERFCTR_UNKNOWN_ca =0xca , + M1_PMU_PERFCTR_UNKNOWN_cb =0xcb , + M1_PMU_PERFCTR_UNKNOWN_f5 =0xf5 , + M1_PMU_PERFCTR_UNKNOWN_f6 =0xf6 , + M1_PMU_PERFCTR_UNKNOWN_f7 =0xf7 , + M1_PMU_PERFCTR_UNKNOWN_f8 =0xf8 , + M1_PMU_PERFCTR_UNKNOWN_fd =0xfd , +M1_PMU_PERFCTR_LAST =M1_PMU_CFG_EVENT , + +/* +* From this point onwards, these are not actual HW events, +* but attributes that get stored in hw->config_base. +*/ +M1_PMU_CFG_COUNT_USER =BIT (8 ), +M1_PMU_CFG_COUNT_KERNEL =BIT (9 ), +}; + +/* +* Per-event affinity table. Most events can be installed on counter +* 2-9, but there are a numbre of exceptions. Note that this table +* has been created experimentally, and I wouldn't be surprised if more +* counters had strange affinities. +*/ +static const u16 m1_pmu_event_affinity[M1_PMU_PERFCTR_LAST +1 ] = { + [0 ...M1_PMU_PERFCTR_LAST ] =ANY_BUT_0_1 , + [M1_PMU_PERFCTR_UNKNOWN_01 ] =BIT (7 ), + [M1_PMU_PERFCTR_CPU_CYCLES ] =ANY_BUT_0_1 |BIT (0 ), + [M1_PMU_PERFCTR_INSTRUCTIONS ] =BIT (7 ) |BIT (1 ), + [M1_PMU_PERFCTR_UNKNOWN_8d] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_8e] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_8f] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_90 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_93 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_94 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_95 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_96 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_97 ] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_98 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_99 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9a] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_9b] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9c] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9f] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_bf] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c0] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c1] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c4] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c5] =ONLY_5_6_7 ,
drivers/perf/apple_m1_cpu_pmu.c line 132
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+ [M1_PMU_PERFCTR_UNKNOWN_c6] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_c8] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_ca] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_cb] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_f5] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f6] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f7] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f8] = ONLY_2_TO_7, + [M1_PMU_PERFCTR_UNKNOWN_fd] = ONLY_2_4_6, +};
I don't entirely follow what's going on here. Is this a matrix scheme like what QC had in their IMP-DEF Krait PMUs? See:
I'm a bit worried about this, since is this is of that shape, there are potential constraints on which counters and/or events you can use concurrently, and if you violate those they can conflict. If so, we need to be *very* careful about the abstraction we provide to userspace.
[...]
Quoted 34 lines
drivers/perf/apple_m1_cpu_pmu.c new file +34
-0+/* Low level accessors. No synchronisation. */ +#define PMU_READ_COUNTER (_idx) \ + case _idx: return read_sysreg_s(SYS_IMP_APL_PMC## _idx ##_EL1) + +#define PMU_WRITE_COUNTER (_val, _idx) \ + case _idx: \ + write_sysreg_s(_val, SYS_IMP_APL_PMC## _idx ##_EL1); \ + return + +static u64 m1_pmu_read_hw_counter (unsigned int index) +{ +switch (index) { +PMU_READ_COUNTER (0 ); +PMU_READ_COUNTER (1 ); +PMU_READ_COUNTER (2 ); +PMU_READ_COUNTER (3 ); +PMU_READ_COUNTER (4 ); +PMU_READ_COUNTER (5 ); +PMU_READ_COUNTER (6 ); +PMU_READ_COUNTER (7 ); +PMU_READ_COUNTER (8 ); +PMU_READ_COUNTER (9 ); + } + +BUG (); +} + +static void m1_pmu_write_hw_counter (u64 val,unsigned int index) +{ +switch (index) { +PMU_WRITE_COUNTER (val,0 ); +PMU_WRITE_COUNTER (val,1 ); +PMU_WRITE_COUNTER (val,2 ); +PMU_WRITE_COUNTER (val,3 );
drivers/perf/apple_m1_cpu_pmu.c line 222
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+PMU_WRITE_COUNTER (val,4 ); +PMU_WRITE_COUNTER (val,5 ); +PMU_WRITE_COUNTER (val,6 ); +PMU_WRITE_COUNTER (val,7 ); +PMU_WRITE_COUNTER (val,8 ); +PMU_WRITE_COUNTER (val,9 ); + } + +BUG (); +}
As an aside, since this pattern has cropped up in a few places, maybe we want to look into scripting the generation of sysreg banki accessors like this.
[...]
Quoted 5 lines
drivers/perf/apple_m1_cpu_pmu.c new file +5
-0+static void m1_pmu_configure_counter (unsigned int index,u8 event, +bool user,bool kernel) +{ +u64 val, user_bit, kernel_bit; +int shift;
drivers/perf/apple_m1_cpu_pmu.c line 310
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+ +switch (index) { + case 0 ... 7: + user_bit =BIT (get_bit_offset (index,PMCR1_COUNT_A64_EL0_0_7 )); + kernel_bit =BIT (get_bit_offset (index,PMCR1_COUNT_A64_EL1_0_7 )); +break ; + case 8 ... 9: + user_bit =BIT (get_bit_offset (index -8 ,PMCR1_COUNT_A64_EL0_8_9 )); + kernel_bit =BIT (get_bit_offset (index -8 ,PMCR1_COUNT_A64_EL1_8_9 )); +break ;
When this says 'EL1', presuambly that's counting at EL2 in VHE?
Are there separate EL1 / EL2 controls, or anythign of that sort we need to be aware of?
[...]
Quoted 4 lines
drivers/perf/apple_m1_cpu_pmu.c new file +4
-0+/* arm_pmu backend */ +static void m1_pmu_enable_event (struct perf_event *event) +{ +struct arm_pmu *cpu_pmu =to_arm_pmu (event->pmu);
drivers/perf/apple_m1_cpu_pmu.c line 368
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+struct pmu_hw_events *cpuc =this_cpu_ptr (cpu_pmu->hw_events); +unsigned long flags; +bool user, kernel; +u8 evt; + + evt = event->hw.config_base &M1_PMU_CFG_EVENT ; + user = event->hw.config_base &M1_PMU_CFG_COUNT_USER ; + kernel = event->hw.config_base &M1_PMU_CFG_COUNT_KERNEL ; + +raw_spin_lock_irqsave (&cpuc->pmu_lock, flags);
You shouldn't need this locking. The perf core always calls into the HW access functions with IRQs disabled and we don't do cross-cpu state modification. Likewise elsewhere in this file.
We pulled similar out of the architectural PMU driver in commit:
2a0e2a02e4b71917 ("arm64: perf: Remove PMU locking")
... though that says non-preemptible when it should say non-interruptible.
I should clean up the 32-bit drivers and remove pmu_hw_events::pmu_lock entirely.
Quoted 22 lines
drivers/perf/apple_m1_cpu_pmu.c new file +22
-0+ +m1_pmu_disable_counter_interrupt (event->hw.idx); +m1_pmu_disable_counter (event->hw.idx); +isb (); + +m1_pmu_configure_counter (event->hw.idx, evt, user, kernel); +m1_pmu_enable_counter (event->hw.idx); +m1_pmu_enable_counter_interrupt (event->hw.idx); +isb (); + +raw_spin_unlock_irqrestore (&cpuc->pmu_lock, flags); +} + +static void __m1_pmu_disable_event (struct perf_event *event) +{ +m1_pmu_disable_counter_interrupt (event->hw.idx); +m1_pmu_disable_counter (event->hw.idx); +isb (); +} + +static void m1_pmu_disable_event (struct perf_event *event) +{
drivers/perf/apple_m1_cpu_pmu.c line 400
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+struct arm_pmu *cpu_pmu =to_arm_pmu (event->pmu); +struct pmu_hw_events *cpuc =this_cpu_ptr (cpu_pmu->hw_events); +unsigned long flags; + +raw_spin_lock_irqsave (&cpuc->pmu_lock, flags); + +__m1_pmu_disable_event (event); + +raw_spin_unlock_irqrestore (&cpuc->pmu_lock, flags); +}
As with m1_pmu_enable_event(), I don't believe the locking is necessary here.
drivers/perf/apple_m1_cpu_pmu.c line 411
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+static irqreturn_t m1_pmu_handle_irq (struct arm_pmu *cpu_pmu) +{ +struct pmu_hw_events *cpuc =this_cpu_ptr (cpu_pmu->hw_events); +irqreturn_t ret =IRQ_HANDLED ; +struct pt_regs *regs; +u64 overflow, state; +unsigned long flags; +int idx; + +raw_spin_lock_irqsave (&cpuc->pmu_lock, flags);
Likewise, no need for a lock here, and certainly not an irqsave!
Same comment for subsequent usage in this file.
drivers/perf/apple_m1_cpu_pmu.c line 413
Quoted 2 lines
drivers/perf/apple_m1_cpu_pmu.c new file +2
-0+ state =read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ); + overflow =read_sysreg_s (SYS_IMP_APL_PMSR_EL1 );
I assume the overflow behaviour is free-running rather than stopping?
Quoted 32 lines
drivers/perf/apple_m1_cpu_pmu.c new file +32
-0+if (!overflow) { + ret =IRQ_NONE ; + goto out; + } + + regs =get_irq_regs (); + +for (idx =0 ; idx < cpu_pmu->num_events; idx++) { +struct perf_event *event = cpuc->events[idx]; +struct perf_sample_data data; + +if (!event) +continue ; + +armpmu_event_update (event); +perf_sample_data_init (&data,0 , event->hw.last_period); +if (!armpmu_event_set_period (event)) +continue ; + +if (perf_event_overflow (event, &data, regs)) +__m1_pmu_disable_event (event); + } + +out: + state &= ~PMCR0_IACT ; +write_sysreg_s (state,SYS_IMP_APL_PMCR0_EL1 ); +isb (); + +raw_spin_unlock_irqrestore (&cpuc->pmu_lock, flags); + +return ret; +}
[...]
Quoted 5 lines
drivers/perf/apple_m1_cpu_pmu.c new file +5
-0+static int m1_pmu_device_probe (struct platform_device *pdev) +{ +int ret; + + ret =arm_pmu_device_probe (pdev, m1_pmu_of_device_ids,NULL );
drivers/perf/apple_m1_cpu_pmu.c line 625
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+if (!ret) { +/* +* If probe succeeds, taint the kernel as this is all +* undocumented, implementation defined black magic. +*/ +add_taint (TAINT_CPU_OUT_OF_SPEC ,LOCKDEP_STILL_OK ); + } + +return ret; +}
Hmmm... that means we're always going to TAINT on this HW with an appropriate DT, which could mask other reasons TAINT_CPU_OUT_OF_SPEC would be set, even where the user isn't using the PMU.
Maybe we should have a cmdline option to opt-in to using the IMP-DEF PMU (and only tainting in that case)?
Thanks,
Mark.
Re: [PATCH v2 8/8] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
Quoted 10 lines
Quoted 4 lines
Add a new, weird and wonderful driver for the equally weird Apple PMU HW. Although the PMU itself is functional, we don't know much about the events yet, so this can be considered as yet another random number generator...
It's really frustrating that Apple built this rather than the architected PMU, because we've generally pushed back on IMPLEMENTATION DEFINED junk in this area, and supporting this makes it harder to push back on other vendors going the same route, which I'm not keen on. That, and the usual state of IMP-DEF stuff making this stupidly painful to reason about.
Rules can be a bit stricter for vendors than for ragtag reverse-engineers. The kernel community can push back on vendor's choices because vendors have the power to choose otherwise. But reverse engineers' hands are sometimes forced by bad vendor decisions; rejecting the driver means mainline can never support the hardware. I believe there's precedent for distinguishing these cases, at least in the graphics subsystem.
I don't know if this applies to this driver. I only wish to offer a rebuttal to a future vendor trying to mainline something questionable with the defence "Asahi Linux / Nouveau / ... did it, so we can too".
(This will be relevant to the Apple M1 display controller driver, which would be a hard NAK if submitted by Apple...)
Re: [PATCH v2 8/8] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
In reply to Mark RutlandQuoted 7 lines · Mark Rutland
Quoted 4 lines · Marc Zyngier
Add a new, weird and wonderful driver for the equally weird Apple PMU HW. Although the PMU itself is functional, we don't know much about the events yet, so this can be considered as yet another random number generator...
Quoted 6 lines
It's really frustrating that Apple built this rather than the architected PMU, because we've generally pushed back on IMPLEMENTATION DEFINED junk in this area, and supporting this makes it harder to push back on other vendors going the same route, which I'm not keen on. That, and the usual state of IMP-DEF stuff making this stupidly painful to reason about.
As much as I agree with you on the stinking aspect of an IMPDEF PMU, this doesn't contradicts the architecture. To avoid the spread of this madness, forbidding an IMPDEF implementation in the architecture would be the right thing to do.
Quoted 5 lines
I can see that we can get this working bare-metal with DT, but I really don't want to try to support this in other cases (e.g. in a VM, potentially with ACPI), or this IMP-DEFness is going to spread more throughout the
arm_pmucode.
Well, an alternative would be to sidestep the arm_pmu framework altogether. Which would probably suck even more.
Quoted 1 line
How does this interact with PMU emulation for a KVM guest?
It doesn't. No non-architected PMU will get exposed to a KVM guest, and the usual "inject an UNDEF exception on IMPDEF access" applies. As far as I am concerned, KVM is purely architectural and doesn't need to be encumbered with this.
Quoted 5 lines
I have a bunch of comments and questions below.
[...]
Quoted 7 lines
drivers/perf/apple_m1_cpu_pmu.c line 28
Quoted 4 lines
drivers/perf/apple_m1_cpu_pmu.c new file +4
-0+#define ANY_BUT_0_1 GENMASK(9, 2) +#define ONLY_2_TO_7 GENMASK(7, 2) +#define ONLY_2_4_6 (BIT(2) | BIT(4) | BIT(6)) +#define ONLY_5_6_7 GENMASK(7, 5)For clarity/consistency it might be better to use separate BIT()s for
ONLY_5_6_7too.
Sure.
[...]
Quoted 39 lines
Quoted 25 lines
drivers/perf/apple_m1_cpu_pmu.c new file +25
-0+static const u16 m1_pmu_event_affinity[M1_PMU_PERFCTR_LAST +1 ] = { + [0 ...M1_PMU_PERFCTR_LAST ] =ANY_BUT_0_1 , + [M1_PMU_PERFCTR_UNKNOWN_01 ] =BIT (7 ), + [M1_PMU_PERFCTR_CPU_CYCLES ] =ANY_BUT_0_1 |BIT (0 ), + [M1_PMU_PERFCTR_INSTRUCTIONS ] =BIT (7 ) |BIT (1 ), + [M1_PMU_PERFCTR_UNKNOWN_8d] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_8e] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_8f] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_90 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_93 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_94 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_95 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_96 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_97 ] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_98 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_99 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9a] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_9b] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9c] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9f] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_bf] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c0] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c1] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c4] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c5] =ONLY_5_6_7 ,drivers/perf/apple_m1_cpu_pmu.c line 132
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+ [M1_PMU_PERFCTR_UNKNOWN_c6] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_c8] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_ca] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_cb] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_f5] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f6] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f7] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f8] = ONLY_2_TO_7, + [M1_PMU_PERFCTR_UNKNOWN_fd] = ONLY_2_4_6, +};I don't entirely follow what's going on here. Is this a matrix scheme like what QC had in their IMP-DEF Krait PMUs? See:
Quoted 1 line
It is nowhere as complicated as that.
Quoted 5 lines
I'm a bit worried about this, since is this is of that shape, there are potential constraints on which counters and/or events you can use concurrently, and if you violate those they can conflict. If so, we need to be *very* careful about the abstraction we provide to userspace.
The HW does have placement constraints (this is what this per-event bitmap is expressing), but the counting seems completely independent as long as you find an ad-hoc counter to place the event. Which means that if you try and count (for example) 4 events that would only fit in {5,6,7}, we'll say NO to the fourth one.
As I say somewhere in a comment, we could do a better job if we had a global view of the events to be counted, and split them in batches that the core perf would then schedule.
If you think any of this somehow breaks the userspace ABI, please let me know (my understand of perf is pretty limited...).
Quoted 62 lines
[...]
Quoted 34 lines
drivers/perf/apple_m1_cpu_pmu.c new file +34
-0+/* Low level accessors. No synchronisation. */ +#define PMU_READ_COUNTER (_idx) \ + case _idx: return read_sysreg_s(SYS_IMP_APL_PMC## _idx ##_EL1) + +#define PMU_WRITE_COUNTER (_val, _idx) \ + case _idx: \ + write_sysreg_s(_val, SYS_IMP_APL_PMC## _idx ##_EL1); \ + return + +static u64 m1_pmu_read_hw_counter (unsigned int index) +{ +switch (index) { +PMU_READ_COUNTER (0 ); +PMU_READ_COUNTER (1 ); +PMU_READ_COUNTER (2 ); +PMU_READ_COUNTER (3 ); +PMU_READ_COUNTER (4 ); +PMU_READ_COUNTER (5 ); +PMU_READ_COUNTER (6 ); +PMU_READ_COUNTER (7 ); +PMU_READ_COUNTER (8 ); +PMU_READ_COUNTER (9 ); + } + +BUG (); +} + +static void m1_pmu_write_hw_counter (u64 val,unsigned int index) +{ +switch (index) { +PMU_WRITE_COUNTER (val,0 ); +PMU_WRITE_COUNTER (val,1 ); +PMU_WRITE_COUNTER (val,2 ); +PMU_WRITE_COUNTER (val,3 );drivers/perf/apple_m1_cpu_pmu.c line 222
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+PMU_WRITE_COUNTER (val,4 ); +PMU_WRITE_COUNTER (val,5 ); +PMU_WRITE_COUNTER (val,6 ); +PMU_WRITE_COUNTER (val,7 ); +PMU_WRITE_COUNTER (val,8 ); +PMU_WRITE_COUNTER (val,9 ); + } + +BUG (); +}As an aside, since this pattern has cropped up in a few places, maybe we want to look into scripting the generation of sysreg banki accessors like this.
[...]
Quoted 9 lines
drivers/perf/apple_m1_cpu_pmu.c new file +9
-0+static void m1_pmu_configure_counter (unsigned int index,u8 event, +bool user,bool kernel) +{ +u64 val, user_bit, kernel_bit; +int shift; + +switch (index) { + case 0 ... 7: + user_bit =BIT (get_bit_offset (index,PMCR1_COUNT_A64_EL0_0_7 ));
Quoted 8 lines
drivers/perf/apple_m1_cpu_pmu.c line 310
Quoted 6 lines
drivers/perf/apple_m1_cpu_pmu.c new file +6
-0+ kernel_bit =BIT (get_bit_offset (index,PMCR1_COUNT_A64_EL1_0_7 )); +break ; + case 8 ... 9: + user_bit =BIT (get_bit_offset (index -8 ,PMCR1_COUNT_A64_EL0_8_9 )); + kernel_bit =BIT (get_bit_offset (index -8 ,PMCR1_COUNT_A64_EL1_8_9 )); +break ;When this says 'EL1', presuambly that's counting at EL2 in VHE?
It does.
Quoted 2 lines
Are there separate EL1 / EL2 controls, or anythign of that sort we need to be aware of?
No, there is a single, per-counter control for EL0 and EL2. I couldn't get the counters to report anything useful while a guest was running, but that doesn't mean such control doesn't exist.
Quoted 22 lines
[...]
Quoted 4 lines
drivers/perf/apple_m1_cpu_pmu.c new file +4
-0+/* arm_pmu backend */ +static void m1_pmu_enable_event (struct perf_event *event) +{ +struct arm_pmu *cpu_pmu =to_arm_pmu (event->pmu);drivers/perf/apple_m1_cpu_pmu.c line 368
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+struct pmu_hw_events *cpuc =this_cpu_ptr (cpu_pmu->hw_events); +unsigned long flags; +bool user, kernel; +u8 evt; + + evt = event->hw.config_base &M1_PMU_CFG_EVENT ; + user = event->hw.config_base &M1_PMU_CFG_COUNT_USER ; + kernel = event->hw.config_base &M1_PMU_CFG_COUNT_KERNEL ; + +raw_spin_lock_irqsave (&cpuc->pmu_lock, flags);You shouldn't need this locking. The perf core always calls into the HW access functions with IRQs disabled and we don't do cross-cpu state modification. Likewise elsewhere in this file.
Quoted 5 lines
We pulled similar out of the architectural PMU driver in commit:
2a0e2a02e4b71917("arm64: perf: Remove PMU locking")... though that says non-preemptible when it should say non-interruptible.
Ah, nice. I'll get rid of it.
[...]
Quoted 4 lines
drivers/perf/apple_m1_cpu_pmu.c line 413
Quoted 2 lines
drivers/perf/apple_m1_cpu_pmu.c new file +2
-0+ state =read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ); + overflow =read_sysreg_s (SYS_IMP_APL_PMSR_EL1 );I assume the overflow behaviour is free-running rather than stopping?
Configurable, apparently. At the moment, I set it to stop on overflow. Happy to change the behaviour though.
Quoted 55 lines
Quoted 32 lines
drivers/perf/apple_m1_cpu_pmu.c new file +32
-0+if (!overflow) { + ret =IRQ_NONE ; + goto out; + } + + regs =get_irq_regs (); + +for (idx =0 ; idx < cpu_pmu->num_events; idx++) { +struct perf_event *event = cpuc->events[idx]; +struct perf_sample_data data; + +if (!event) +continue ; + +armpmu_event_update (event); +perf_sample_data_init (&data,0 , event->hw.last_period); +if (!armpmu_event_set_period (event)) +continue ; + +if (perf_event_overflow (event, &data, regs)) +__m1_pmu_disable_event (event); + } + +out: + state &= ~PMCR0_IACT ; +write_sysreg_s (state,SYS_IMP_APL_PMCR0_EL1 ); +isb (); + +raw_spin_unlock_irqrestore (&cpuc->pmu_lock, flags); + +return ret; +}[...]
Quoted 5 lines
drivers/perf/apple_m1_cpu_pmu.c new file +5
-0+static int m1_pmu_device_probe (struct platform_device *pdev) +{ +int ret; + + ret =arm_pmu_device_probe (pdev, m1_pmu_of_device_ids,NULL );drivers/perf/apple_m1_cpu_pmu.c line 625
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+if (!ret) { +/* +* If probe succeeds, taint the kernel as this is all +* undocumented, implementation defined black magic. +*/ +add_taint (TAINT_CPU_OUT_OF_SPEC ,LOCKDEP_STILL_OK ); + } + +return ret; +}Hmmm... that means we're always going to TAINT on this HW with an appropriate DT, which could mask other reasons
TAINT_CPU_OUT_OF_SPECwould be set, even where the user isn't using the PMU.
Quoted 2 lines
Maybe we should have a cmdline option to opt-in to using the IMP-DEF PMU (and only tainting in that case)?
I'd rather taint on first use. Requiring a command-line argument for this seems a bit over the top...
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Mark Rutland
maintainerRe: [PATCH v2 8/8] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
Quoted 16 lines · Marc Zyngier
Quoted 7 lines · Mark Rutland
Quoted 4 lines · Marc Zyngier
Add a new, weird and wonderful driver for the equally weird Apple PMU HW. Although the PMU itself is functional, we don't know much about the events yet, so this can be considered as yet another random number generator...
Quoted 6 lines
It's really frustrating that Apple built this rather than the architected PMU, because we've generally pushed back on IMPLEMENTATION DEFINED junk in this area, and supporting this makes it harder to push back on other vendors going the same route, which I'm not keen on. That, and the usual state of IMP-DEF stuff making this stupidly painful to reason about.
Quoted 4 lines
As much as I agree with you on the stinking aspect of an IMPDEF PMU, this doesn't contradicts the architecture. To avoid the spread of this madness, forbidding an IMPDEF implementation in the architecture would be the right thing to do.
Yeah; I'll see what I can do. ;)
Quoted 8 lines
Quoted 4 lines
I can see that we can get this working bare-metal with DT, but I really don't want to try to support this in other cases (e.g. in a VM, potentially with ACPI), or this IMP-DEFness is going to spread more throughout the
arm_pmucode.Well, an alternative would be to sidestep the
arm_pmuframework altogether. Which would probably suck even more.
Quoted 6 lines
Quoted 1 line
How does this interact with PMU emulation for a KVM guest?
It doesn't. No non-architected PMU will get exposed to a KVM guest, and the usual "inject an UNDEF exception on IMPDEF access" applies. As far as I am concerned, KVM is purely architectural and doesn't need to be encumbered with this.
Cool; I think not exposing this into a VM rules out the other issues I was concerned with, so as long as we're ruling that out I think we're agreed (and I see no reason for us to try to force this platform to work with ACPI on bare-metal).
Quoted 39 lines
Quoted 39 lines
Quoted 25 lines
drivers/perf/apple_m1_cpu_pmu.c new file +25
-0+static const u16 m1_pmu_event_affinity[M1_PMU_PERFCTR_LAST +1 ] = { + [0 ...M1_PMU_PERFCTR_LAST ] =ANY_BUT_0_1 , + [M1_PMU_PERFCTR_UNKNOWN_01 ] =BIT (7 ), + [M1_PMU_PERFCTR_CPU_CYCLES ] =ANY_BUT_0_1 |BIT (0 ), + [M1_PMU_PERFCTR_INSTRUCTIONS ] =BIT (7 ) |BIT (1 ), + [M1_PMU_PERFCTR_UNKNOWN_8d] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_8e] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_8f] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_90 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_93 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_94 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_95 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_96 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_97 ] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_98 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_99 ] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9a] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_9b] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9c] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_9f] =BIT (7 ), + [M1_PMU_PERFCTR_UNKNOWN_bf] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c0] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c1] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c4] =ONLY_5_6_7 , + [M1_PMU_PERFCTR_UNKNOWN_c5] =ONLY_5_6_7 ,drivers/perf/apple_m1_cpu_pmu.c line 132
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+ [M1_PMU_PERFCTR_UNKNOWN_c6] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_c8] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_ca] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_cb] = ONLY_5_6_7, + [M1_PMU_PERFCTR_UNKNOWN_f5] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f6] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f7] = ONLY_2_4_6, + [M1_PMU_PERFCTR_UNKNOWN_f8] = ONLY_2_TO_7, + [M1_PMU_PERFCTR_UNKNOWN_fd] = ONLY_2_4_6, +};I don't entirely follow what's going on here. Is this a matrix scheme like what QC had in their IMP-DEF Krait PMUs? See:
Quoted 3 lines
Quoted 1 line
It is nowhere as complicated as that.
Good to hear!
Quoted 12 lines
Quoted 5 lines
I'm a bit worried about this, since is this is of that shape, there are potential constraints on which counters and/or events you can use concurrently, and if you violate those they can conflict. If so, we need to be *very* careful about the abstraction we provide to userspace.
The HW does have placement constraints (this is what this per-event bitmap is expressing), but the counting seems completely independent as long as you find an ad-hoc counter to place the event. Which means that if you try and count (for example) 4 events that would only fit in {5,6,7}, we'll say NO to the fourth one.
Quoted 3 lines
As I say somewhere in a comment, we could do a better job if we had a global view of the events to be counted, and split them in batches that the core perf would then schedule.
For better or worse I don't think there's a good way to do that due to the way the core perf event lists are managed. You basically have a choice between either stopping prematurely or iterating over *all* the events redundantly (which is potentially very expensive and deliberately avoided today).
If (as I understand from the above) the constraints are independent then I don't think there's anything we can do in the PMU driver.
Quoted 2 lines
If you think any of this somehow breaks the userspace ABI, please let me know (my understand of perf is pretty limited...).
As long as there are no cross-event or cross-counter constraints, then I don't think there's a userspace ABI problem here.
[...]
Quoted 18 lines
Quoted 9 lines
Quoted 9 lines
drivers/perf/apple_m1_cpu_pmu.c new file +9
-0+static void m1_pmu_configure_counter (unsigned int index,u8 event, +bool user,bool kernel) +{ +u64 val, user_bit, kernel_bit; +int shift; + +switch (index) { + case 0 ... 7: + user_bit =BIT (get_bit_offset (index,PMCR1_COUNT_A64_EL0_0_7 ));Quoted 8 lines
drivers/perf/apple_m1_cpu_pmu.c line 310
Quoted 6 lines
drivers/perf/apple_m1_cpu_pmu.c new file +6
-0+ kernel_bit =BIT (get_bit_offset (index,PMCR1_COUNT_A64_EL1_0_7 )); +break ; + case 8 ... 9: + user_bit =BIT (get_bit_offset (index -8 ,PMCR1_COUNT_A64_EL0_8_9 )); + kernel_bit =BIT (get_bit_offset (index -8 ,PMCR1_COUNT_A64_EL1_8_9 )); +break ;When this says 'EL1', presuambly that's counting at EL2 in VHE?
Quoted 8 lines
It does.
Quoted 2 lines
Are there separate EL1 / EL2 controls, or anythign of that sort we need to be aware of?
No, there is a single, per-counter control for EL0 and EL2. I couldn't get the counters to report anything useful while a guest was running, but that doesn't mean such control doesn't exist.
Ok. We might need to require the exclude_guest flag for now, assuming the perf tool automatically sets that.
[...]
Quoted 7 lines
Quoted 4 lines
drivers/perf/apple_m1_cpu_pmu.c line 413
Quoted 2 lines
drivers/perf/apple_m1_cpu_pmu.c new file +2
-0+ state =read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ); + overflow =read_sysreg_s (SYS_IMP_APL_PMSR_EL1 );I assume the overflow behaviour is free-running rather than stopping?
Configurable, apparently. At the moment, I set it to stop on overflow. Happy to change the behaviour though.
The architected PMU continues counting upon overflow (which prevents losing counts around the overlflow occurring), so I'd prefer that.
Is that behaviour per-counter, or for the PMU as a whole?
[...]
Quoted 20 lines
Quoted 20 lines
Quoted 5 lines
drivers/perf/apple_m1_cpu_pmu.c new file +5
-0+static int m1_pmu_device_probe (struct platform_device *pdev) +{ +int ret; + + ret =arm_pmu_device_probe (pdev, m1_pmu_of_device_ids,NULL );drivers/perf/apple_m1_cpu_pmu.c line 625
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+if (!ret) { +/* +* If probe succeeds, taint the kernel as this is all +* undocumented, implementation defined black magic. +*/ +add_taint (TAINT_CPU_OUT_OF_SPEC ,LOCKDEP_STILL_OK ); + } + +return ret; +}Hmmm... that means we're always going to TAINT on this HW with an appropriate DT, which could mask other reasons
TAINT_CPU_OUT_OF_SPECwould be set, even where the user isn't using the PMU.
Quoted 5 lines
Quoted 2 lines
Maybe we should have a cmdline option to opt-in to using the IMP-DEF PMU (and only tainting in that case)?
I'd rather taint on first use. Requiring a command-line argument for this seems a bit over the top...
That does sound nicer.
That said, if we've probed the thing, we're going to be poking it to reset it (including out of idle), even if the user hasn't tried to use it, so I'm not sure what's best after all...
Thanks,
Mark.
Re: [PATCH v2 8/8] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
Quoted 40 lines · Mark Rutland
Quoted 16 lines · Marc Zyngier
Quoted 7 lines · Mark Rutland
Quoted 4 lines · Marc Zyngier
Add a new, weird and wonderful driver for the equally weird Apple PMU HW. Although the PMU itself is functional, we don't know much about the events yet, so this can be considered as yet another random number generator...
Quoted 6 lines
It's really frustrating that Apple built this rather than the architected PMU, because we've generally pushed back on IMPLEMENTATION DEFINED junk in this area, and supporting this makes it harder to push back on other vendors going the same route, which I'm not keen on. That, and the usual state of IMP-DEF stuff making this stupidly painful to reason about.
Quoted 4 lines
As much as I agree with you on the stinking aspect of an IMPDEF PMU, this doesn't contradicts the architecture. To avoid the spread of this madness, forbidding an IMPDEF implementation in the architecture would be the right thing to do.
Yeah; I'll see what I can do. ;)
Quoted 8 lines
Quoted 4 lines
I can see that we can get this working bare-metal with DT, but I really don't want to try to support this in other cases (e.g. in a VM, potentially with ACPI), or this IMP-DEFness is going to spread more throughout the
arm_pmucode.Well, an alternative would be to sidestep the
arm_pmuframework altogether. Which would probably suck even more.Quoted 6 lines
Quoted 1 line
How does this interact with PMU emulation for a KVM guest?
It doesn't. No non-architected PMU will get exposed to a KVM guest, and the usual "inject an UNDEF exception on IMPDEF access" applies. As far as I am concerned, KVM is purely architectural and doesn't need to be encumbered with this.
Quoted 4 lines
Cool; I think not exposing this into a VM rules out the other issues I was concerned with, so as long as we're ruling that out I think we're agreed (and I see no reason for us to try to force this platform to work with ACPI on bare-metal).
Nah. This is a tortuous enough system.
Quoted 6 lines
Quoted 3 lines
No, there is a single, per-counter control for EL0 and EL2. I couldn't get the counters to report anything useful while a guest was running, but that doesn't mean such control doesn't exist.
Ok. We might need to require the
exclude_guestflag for now, assuming the perf tool automatically sets that.
OK.
Quoted 8 lines
[...]
Quoted 5 lines
Quoted 4 lines
drivers/perf/apple_m1_cpu_pmu.c line 413
Quoted 2 lines
drivers/perf/apple_m1_cpu_pmu.c new file +2
-0+ state =read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ); + overflow =read_sysreg_s (SYS_IMP_APL_PMSR_EL1 );I assume the overflow behaviour is free-running rather than stopping?
Quoted 7 lines
Quoted 2 lines
Configurable, apparently. At the moment, I set it to stop on overflow. Happy to change the behaviour though.
The architected PMU continues counting upon overflow (which prevents losing counts around the overlflow occurring), so I'd prefer that.
Is that behaviour per-counter, or for the PMU as a whole?
It is global. This will probably require some additional rework to clear bit 47 in overflowing counters, which we can't do atomically.
Quoted 26 lines
[...]
Quoted 23 lines
Quoted 22 lines
Quoted 5 lines
drivers/perf/apple_m1_cpu_pmu.c new file +5
-0+static int m1_pmu_device_probe (struct platform_device *pdev) +{ +int ret; + + ret =arm_pmu_device_probe (pdev, m1_pmu_of_device_ids,NULL );drivers/perf/apple_m1_cpu_pmu.c line 625
Quoted 10 lines
drivers/perf/apple_m1_cpu_pmu.c new file +10
-0+if (!ret) { +/* +* If probe succeeds, taint the kernel as this is all +* undocumented, implementation defined black magic. +*/ +add_taint (TAINT_CPU_OUT_OF_SPEC ,LOCKDEP_STILL_OK ); + } + +return ret; +}Hmmm... that means we're always going to TAINT on this HW with an appropriate DT, which could mask other reasons
TAINT_CPU_OUT_OF_SPECwould be set, even where the user isn't using the PMU.Maybe we should have a cmdline option to opt-in to using the IMP-DEF PMU (and only tainting in that case)?
Quoted 8 lines
Quoted 2 lines
I'd rather taint on first use. Requiring a command-line argument for this seems a bit over the top...
That does sound nicer.
That said, if we've probed the thing, we're going to be poking it to reset it (including out of idle), even if the user hasn't tried to use it, so I'm not sure what's best after all...
Yup, there is that. I'll have another look.
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Mark Rutland
maintainerRe: [PATCH v2 8/8] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
Quoted 12 lines · Marc Zyngier
Quoted 11 lines · Mark Rutland
Quoted 9 lines · Marc Zyngier
Quoted 5 lines · Mark Rutland
drivers/perf/apple_m1_cpu_pmu.c line 413
Quoted 2 lines · Marc Zyngier
drivers/perf/apple_m1_cpu_pmu.c new file +2
-0+ state =read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ); + overflow =read_sysreg_s (SYS_IMP_APL_PMSR_EL1 );I assume the overflow behaviour is free-running rather than stopping?
Configurable, apparently. At the moment, I set it to stop on overflow. Happy to change the behaviour though.
Quoted 7 lines
Quoted 4 lines
The architected PMU continues counting upon overflow (which prevents losing counts around the overlflow occurring), so I'd prefer that.
Is that behaviour per-counter, or for the PMU as a whole?
It is global. This will probably require some additional rework to clear bit 47 in overflowing counters, which we can't do atomically.
Ah; I see.
To calrify my comment above, the reason for wanting the counter to keep counting is to count during the window between the IRQ being asserted and the PMU IRQ handler being invoked, and it's fine for there to be a blackout period *within* the PMU IRQ handler.
So for example it would be fine to have:
irq_handler()
{
if (!any_counter_overflowed())
return IRQ_NONE;
stop_all_counters();
for_each_counter(c) {
handle_counter(c);
}
start_all_counters();
return IRQ_HANDLED;
}... and I think with that the regular per-counter period reprogramming would do the right thing?
Really, all the PMU drivers should do that so that repgoramming is consistent and we don't get skewed groups.
Thanks,
Mark.
Re: [PATCH v2 8/8] drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
Quoted 48 lines · Mark Rutland
Quoted 12 lines · Marc Zyngier
Quoted 11 lines · Mark Rutland
Quoted 9 lines · Marc Zyngier
Quoted 5 lines · Mark Rutland
drivers/perf/apple_m1_cpu_pmu.c line 413
Quoted 2 lines · Marc Zyngier
drivers/perf/apple_m1_cpu_pmu.c new file +2
-0+ state =read_sysreg_s (SYS_IMP_APL_PMCR0_EL1 ); + overflow =read_sysreg_s (SYS_IMP_APL_PMSR_EL1 );I assume the overflow behaviour is free-running rather than stopping?
Configurable, apparently. At the moment, I set it to stop on overflow. Happy to change the behaviour though.
Quoted 7 lines
Quoted 4 lines
The architected PMU continues counting upon overflow (which prevents losing counts around the overlflow occurring), so I'd prefer that.
Is that behaviour per-counter, or for the PMU as a whole?
It is global. This will probably require some additional rework to clear bit 47 in overflowing counters, which we can't do atomically.
Ah; I see.
To calrify my comment above, the reason for wanting the counter to keep counting is to count during the window between the IRQ being asserted and the PMU IRQ handler being invoked, and it's fine for there to be a blackout period *within* the PMU IRQ handler.
So for example it would be fine to have:
irq_handler() { if (!any_counter_overflowed()) return IRQ_NONE; stop_all_counters(); for_each_counter(c) { handle_counter(c); } start_all_counters(); return IRQ_HANDLED; }
Quoted 2 lines
... and I think with that the regular per-counter period reprogramming would do the right thing?
Yup. It looks like this works just fine.
Thanks,
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.