[lkml]   [2019]   [Dec]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[PATCH v2 0/6] arm64: ARMv8.4 Activity Monitors support
These patches introduce support for the Activity Monitors Unit (AMU)
CPU extension, an optional extension in ARMv8.4 CPUs. This provides
performance counters intended for system management use. Two of these
counters are then used to compute the frequency scale correction
factor needed to achieve frequency invariance.

With the CONFIG_ARM64_AMU_EXTN enabled the kernel is able to safely
run a mix of CPUs with and without support for the AMU extension.
The AMU capability is unconditionally enabled in the kernel as to
allow any late CPU to use the feature: the cpu_enable function will
be called for all CPUs that match the criteria, including secondary
and hotplugged CPUs, marking this feature as present on that
respective CPU (through a per-cpu variable).

To be noted that firmware must implement AMU support when running on
CPUs that present the activity monitors extension: allow access to
the registers from lower exception levels, enable the counters,
implement save and restore functionality. More details can be found
in the documentation.

Given that the activity counters inform on activity on the CPUs, and
that not all CPUs might implement the extension, for functional and
security reasons, it's best to disable access to the AMU registers
from userspace (EL0) and KVM guests.

In the last patch of the series, two of the AMU counters are used to
compute the frequency scale factor needed to achieve frequency
invariance of signals in the scheduler, based on an interface added
to support counter-based frequency invariance - arch_scale_freq_tick.
The interface and update point for the counter-based frequency scale
factor is based on the similar approach in the patch that introduces
frequency invariance for x86 [1].

The current series is based on linux-next 20191217.

- Build tested for multiple architectures and defconfigs.
- AMU feature detection, EL0 and KVM guest access to AMU registers,
feature support in firmware (version 1.5 and later of the ARM
Trusted Firmware) was tested on an Armv8-A Base Platform FVP:
Architecture Envelope Model [2] (supports version 8.0 to 8.5),
with the following configurations:


v1 -> v2:
- v1 can be found at [3]
- Added patches that use the counters for the scheduler's frequency
invariance engine
- In patch arm64: add support for the AMU extension v1 -
- Defined an accessor function cpu_has_amu_feat to allow a read
of amu_feat only from the current CPU, to ensure the safe use
of the per-cpu variable for the current user (arm64 topology
driver) and future users.
- Modified type of amu_feat from bool to u8 to satisfy sparse
checker's warning 'expression using sizeof _Bool [sparse]',
as the size of bool is compiler dependent.


Ionela Voinescu (6):
arm64: add support for the AMU extension v1
arm64: trap to EL1 accesses to AMU counters from EL0
arm64/kvm: disable access to AMU registers from kvm guests
Documentation: arm64: document support for the AMU extension
TEMP: sched: add interface for counter-based frequency invariance
arm64: use activity monitors for frequency invariance

Documentation/arm64/amu.rst | 107 ++++++++
Documentation/arm64/booting.rst | 14 ++
Documentation/arm64/cpu-feature-registers.rst | 2 +
Documentation/arm64/index.rst | 1 +
arch/arm64/Kconfig | 27 ++
arch/arm64/include/asm/assembler.h | 10 +
arch/arm64/include/asm/cpucaps.h | 3 +-
arch/arm64/include/asm/cpufeature.h | 4 +
arch/arm64/include/asm/kvm_arm.h | 7 +-
arch/arm64/include/asm/sysreg.h | 44 ++++
arch/arm64/include/asm/topology.h | 9 +
arch/arm64/kernel/cpufeature.c | 81 +++++-
arch/arm64/kernel/topology.c | 233 ++++++++++++++++++
arch/arm64/kvm/hyp/switch.c | 13 +-
arch/arm64/kvm/sys_regs.c | 95 ++++++-
arch/arm64/mm/proc.S | 3 +
drivers/base/arch_topology.c | 16 ++
kernel/sched/core.c | 1 +
kernel/sched/sched.h | 7 +
19 files changed, 666 insertions(+), 11 deletions(-)
create mode 100644 Documentation/arm64/amu.rst


 \ /
  Last update: 2019-12-18 19:29    [W:0.221 / U:4.276 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site