perf: arm64: Kernel support for Dwarf unwinding through SVE functions
Subsystems (3)
v3 cover perf: arm64: Kernel support for Dwarf unwinding through SVE functions
Hi,
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to output_sample() because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].
[1]: https://lore.kernel.org/lkml/[email protected]/
=======
Changes since v2:
* Add definition for PERF_REG_EXTENDED_MASK which is needed for PERF_PMU_CAP_EXTENDED_REGS to work properly
* Simplify changes to enum perf_event_arm_regs
Changes since v1:
* Add Mark's review tag
* Clarify in docs that it's the SVE register length
* Split patchset into kernel side and Perf tool changes
=======
When SVE registers are pushed onto the stack the VG register is required to unwind because the stack offsets would vary by the SVE register width at the time when the sample was taken.
These first two patches add support for sampling the VG register to the kernel and the docs. There is another patchset to add support to userspace perf.
A small change is also required to libunwind or libdw depending on which unwinder is used, and these will be published later. Without these changes Perf continues to work with both libraries, although the VG register is still not used for unwinding.
Thanks
James
James Clark (2):
perf: arm64: Add SVE vector granule register to user regs arm64/sve: Add Perf extensions documentation
Documentation/arm64/sve.rst | 20 +++++++++++++++++ arch/arm64/include/uapi/asm/perf_regs.h | 7 ++++++ arch/arm64/kernel/perf_regs.c | 30 +++++++++++++++++++++++-- drivers/perf/arm_pmu.c | 2 +- 4 files changed, 56 insertions(+), 3 deletions(-)
Signature · 1 line
2.28.0
PATCH v3 1/2 perf: arm64: Add SVE vector granule register to user regs
Dwarf based unwinding in a function that pushes SVE registers onto the stack requires the unwinder to know the length of the SVE register to calculate the stack offsets correctly. This was added to the Arm specific Dwarf spec as the VG pseudo register[1].
Add the vector length at position 46 if it's requested by userspace and SVE is supported. If it's not supported then fail to open the event.
The vector length must be on each sample because it can be changed at runtime via a prctl or ptrace call. Also by adding it as a register rather than a separate attribute, minimal changes will be required in an unwinder that already indexes into the register list.
[1]: https://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst
--- arch/arm64/include/uapi/asm/perf_regs.h | 7 ++++++ arch/arm64/kernel/perf_regs.c | 30 +++++++++++++++++++++++-- drivers/perf/arm_pmu.c | 2 +- 3 files changed, 36 insertions(+), 3 deletions(-)
arch/arm64/include/uapi/asm/perf_regs.h +7 -0
@@ -37,5 +37,12 @@ enum perf_event_arm_regs {PERF_REG_ARM64_SP ,PERF_REG_ARM64_PC ,PERF_REG_ARM64_MAX , + +/* Extended/pseudo registers */ +PERF_REG_ARM64_VG =46 ,// SVE Vector Granule +PERF_REG_ARM64_EXTENDED_MAX }; + +#define PERF_REG_EXTENDED_MASK (1ULL << PERF_REG_ARM64_VG) +#endif /* _ASM_ARM64_PERF_REGS_H */
arch/arm64/kernel/perf_regs.c +28 -2
@@ -9,9 +9,27 @@#include <asm/perf_regs.h> #include <asm/ptrace.h> +static u64 perf_ext_regs_value (int idx) +{ +switch (idx) { +case PERF_REG_ARM64_VG : +if (WARN_ON_ONCE (!system_supports_sve ())) +return 0 ; + +/* +* Vector granule is current length in bits of SVE registers +* divided by 64. +*/ +return (task_get_sve_vl (current) *8 ) /64 ; +default : +WARN_ON_ONCE (true); +return 0 ; + } +} +u64 perf_reg_value (struct pt_regs *regs,int idx) { -if (WARN_ON_ONCE ((u32 )idx >=PERF_REG_ARM64_MAX )) +if (WARN_ON_ONCE ((u32 )idx >=PERF_REG_ARM64_EXTENDED_MAX ))return 0 ;/*
@@ -51,6 +69,9 @@ u64 perf_reg_value(struct pt_regs *regs, int idx)if ((u32 )idx ==PERF_REG_ARM64_PC )return regs->pc; +if ((u32 )idx >=PERF_REG_ARM64_MAX ) +return perf_ext_regs_value (idx); +return regs->regs[idx]; }
@@ -58,7 +79,12 @@ u64 perf_reg_value(struct pt_regs *regs, int idx)int perf_reg_validate (u64 mask) { -if (!mask || mask ®_RESERVED ) +u64 reserved_mask =REG_RESERVED ; + +if (system_supports_sve ()) + reserved_mask &= ~(1ULL <<PERF_REG_ARM64_VG ); + +if (!mask || mask & reserved_mask)return -EINVAL ;return 0 ;
drivers/perf/arm_pmu.c +1 -1
@@ -894,7 +894,7 @@ static struct arm_pmu *__armpmu_alloc(gfp_t flags)* pmu::filter_match callback and pmu::event_init group * validation). */ - .capabilities = PERF_PMU_CAP_HETEROGENEOUS_CPUS, + .capabilities = PERF_PMU_CAP_HETEROGENEOUS_CPUS | PERF_PMU_CAP_EXTENDED_REGS, }; pmu->attr_groups[ARMPMU_ATTR_GROUP_COMMON] =
Signature · 1 line
2.28.0
PATCH v3 2/2 arm64/sve: Add Perf extensions documentation
In reply to James ClarkDocument that the VG register is available in Perf samples
--- Documentation/arm64/sve.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)
Documentation/arm64/sve.rst +20 -0
@@ -452,6 +452,24 @@ The regset data starts with struct user_sve_header, containing: * Modifying the system default vector length does not affect the vector length of any existing process or thread that does not make an execve() call. +10. Perf extensions +-------------------------------- + +* The arm64 specific DWARF standard [5] added the VG (Vector Granule) register + at index 46. This register is used for DWARF unwinding when variable length + SVE registers are pushed onto the stack. + +* Its value is equivalent to the current SVE vector length (VL) in bits divided + by 64. + +* The value is included in Perf samples in the regs[46] field if + PERF_SAMPLE_REGS_USER is set and the sample_regs_user mask has bit 46 set. + +* The value is the current value at the time the sample was taken, and it can + change over time. + +* If the system doesn't support SVE when perf_event_open is called with these + settings, the event will fail to open. Appendix A. SVE programmer's model (informative) =================================================
@@ -593,3 +611,5 @@ References http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055c/IHI0055C_beta_aapcs64.pdf http://infocenter.arm.com/help/topic/com.arm.doc.subset.swdev.abi/index.html Procedure Call Standard for the ARM 64-bit Architecture (AArch64) + +[5] https://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst
Signature · 1 line
2.28.0
Re: [PATCH v3 2/2] arm64/sve: Add Perf extensions documentation
Quoted 1 line · James Clark
Document that the VG register is available in Perf samples
Re: [PATCH v3 2/2] arm64/sve: Add Perf extensions documentation
Quoted 5 lines · Mark Brown
Quoted 1 line · James Clark
Document that the VG register is available in Perf samples
Reviewed-by Mark Brown <[email protected]>
Hi Will/Mark R,
Is this set ok to go into 6.1?
Thanks
James
Will Deacon
maintainerQuoted 8 lines · James Clark
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to
output_sample()because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].
Fair enough, I can't argue against being consistent.
Given that this exposes subtle new user ABI, do we have any coverage in the selftests? If not, please could you add something?
Thanks,
Will
Quoted 8 lines · Will Deacon
Quoted 7 lines · James Clark
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to
output_sample()because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].
Quoted 7 lines
Quoted 1 line
Fair enough, I can't argue against being consistent.
Given that this exposes subtle new user ABI, do we have any coverage in the selftests? If not, please could you add something?
Thanks, I will do that. I assume you mean the self tests in tools/perf/tests and not some non Perf tests?
Quoted 3 lines
Thanks,
Will
Will Deacon
maintainerQuoted 13 lines · James Clark
Quoted 10 lines · Will Deacon
Quoted 8 lines · James Clark
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to
output_sample()because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].
Quoted 8 lines
Quoted 5 lines
Fair enough, I can't argue against being consistent.
Given that this exposes subtle new user ABI, do we have any coverage in the selftests? If not, please could you add something?
Thanks, I will do that. I assume you mean the self tests in
tools/perf/testsand not some non Perf tests?
I hadn't thought much about it, so wherever is best. It would just be nice to have something we can run to make sure that this continues to work as intended.
Will
Quoted 8 lines · James Clark
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to
output_sample()because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].[...]
Applied to will (for-next/perf), thanks!
[1/2] perf: arm64: Add SVE vector granule register to user regs
https://git.kernel.org/will/c/cbb0c02caf4b [2/2] arm64/sve: Add Perf extensions documentation https://git.kernel.org/will/c/1f2906d1e10a
Cheers,
Signature · 5 lines
Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev
Quoted 10 lines · Will Deacon
Quoted 8 lines · James Clark
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to
output_sample()because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].[...]
Quoted 8 lines
Applied to will (for-next/perf), thanks!
[1/2] perf: arm64: Add SVE vector granule register to user regs
https://git.kernel.org/will/c/cbb0c02caf4b [2/2] arm64/sve: Add Perf extensions documentation https://git.kernel.org/will/c/1f2906d1e10aCheers,
Thanks Will. Sorry about the build, I will fix my config for next time.
Will Deacon
maintainerQuoted 15 lines · James Clark
Quoted 12 lines · Will Deacon
Quoted 8 lines · James Clark
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to
output_sample()because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].[...]
Applied to will (for-next/perf), thanks!
Quoted 8 lines
Quoted 6 lines
[1/2] perf: arm64: Add SVE vector granule register to user regs
https://git.kernel.org/will/c/cbb0c02caf4b [2/2] arm64/sve: Add Perf extensions documentation https://git.kernel.org/will/c/1f2906d1e10aCheers,
Thanks Will. Sorry about the build, I will fix my config for next time.
No problem. For some reason, I was unable to repro the failure locally. Maybe it's a GCC thing?
Will
Quoted 21 lines · Will Deacon
Quoted 20 lines · James Clark
Quoted 17 lines · Will Deacon
Quoted 8 lines · James Clark
I'm resubmitting this with a few of the changes suggested by Will on V2.
I haven't made any changes regarding the open questions about the discoverability or saving the new reg and passing to
output_sample()because I think it's best to be consistent with the implementations on other platforms first. I have explained in more detail on v2 [1].[...]
Applied to will (for-next/perf), thanks!
[1/2] perf: arm64: Add SVE vector granule register to user regs
https://git.kernel.org/will/c/cbb0c02caf4b [2/2] arm64/sve: Add Perf extensions documentation https://git.kernel.org/will/c/1f2906d1e10a
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
Cheers,
Thanks Will. Sorry about the build, I will fix my config for next time.
No problem. For some reason, I was unable to repro the failure locally. Maybe it's a GCC thing?
For me I needed CONFIG_HEADERS_INSTALL and CONFIG_UAPI_HEADER_TEST to reproduce it. I was already using gcc, so not sure if it's depends on that or not.
Quoted 2 lines
Will