On Fri, 14 Jul 2023 11:38:40 +0800, chenxiang wrote: > From: Xiang Chen <chenxiang66@xxxxxxxxxxxxx> > > For those PMU system registers defined in sys_reg_descs[], use macro > PMU_SYS_REG() / PMU_PMEVCNTR_EL0 / PMU_PMEVTYPER_EL0 to define them, and > later two macros call macro PMU_SYS_REG() actually. > Currently the input parameter of PMU_SYS_REG() is another macro which is > calculation formula of the value of system registers, so for example, if > we want to "SYS_PMINTENSET_EL1" as the name of sys register, actually > the name we get is as following: > (((3) << 19) | ((0) << 16) | ((9) << 12) | ((14) << 8) | ((1) << 5)) > The name of system register is used in some tracepoints such as > trace_kvm_sys_access(), if not set correctly, we need to analyze the > inaccurate name to get the exact name (which also is inconsistent with > other system registers), and also the inaccurate name occupies more space. > > [...] Applied to kvmarm/fixes, thanks! [1/1] KVM: arm64: Fix the name of sys_reg_desc related to PMU https://git.kernel.org/kvmarm/kvmarm/c/9d2a55b403ee -- Best, Oliver