Commit 356a1adc authored by Linus Torvalds's avatar Linus Torvalds
Browse files

Merge tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux 

Pull arm64 updates from Will Deacon:

 - Support for including MTE tags in ELF coredumps

 - Instruction encoder updates, including fixes to 64-bit immediate
   generation and support for the LSE atomic instructions

 - Improvements to kselftests for MTE and fpsimd

 - Symbol aliasing and linker script cleanups

 - Reduce instruction cache maintenance performed for user mappings
   created using contiguous PTEs

 - Support for the new "asymmetric" MTE mode, where stores are checked
   asynchronously but loads are checked synchronously

 - Support for the latest pointer authentication algorithm ("QARMA3")

 - Support for the DDR PMU present in the Marvell CN10K platform

 - Support for the CPU PMU present in the Apple M1 platform

 - Use the RNDR instruction for arch_get_random_{int,long}()

 - Update our copy of the Arm optimised string routines for str{n}cmp()

 - Fix signal frame generation for CPUs which have foolishly elected to
   avoid building in support for the fpsimd instructions

 - Workaround for Marvell GICv3 erratum #38545

 - Clarification to our Documentation (booting reqs. and MTE prctl())

 - Miscellanous cleanups and minor fixes

* tag 'arm64-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux: (90 commits)
  docs: sysfs-devices-system-cpu: document "asymm" value for mte_tcf_preferred
  arm64/mte: Remove asymmetric mode from the prctl() interface
  arm64: Add cavium_erratum_23154_cpus missing sentinel
  perf/marvell: Fix !CONFIG_OF build for CN10K DDR PMU driver
  arm64: mm: Drop 'const' from conditional arm64_dma_phys_limit definition
  Documentation: vmcoreinfo: Fix htmldocs warning
  kasan: fix a missing header include of static_keys.h
  drivers/perf: Add Apple icestorm/firestorm CPU PMU driver
  drivers/perf: arm_pmu: Handle 47 bit counters
  arm64: perf: Consistently make all event numbers as 16-bits
  arm64: perf: Expose some Armv9 common events under sysfs
  perf/marvell: cn10k DDR perf event core ownership
  perf/marvell: cn10k DDR perfmon event overflow handling
  perf/marvell: CN10k DDR performance monitor support
  dt-bindings: perf: marvell: cn10k ddr performance monitor
  arm64: clean up tools Makefile
  perf/arm-cmn: Update watchpoint format
  perf/arm-cmn: Hide XP PUB events for CMN-600
  arm64: drop unused includes of <linux/personality.h>
  arm64: Do not defer reserve_crashkernel() for platforms with no DMA memory zones
  ...
parents 9d8e7007 641d8041

Documentation/ABI/testing/sysfs-devices-system-cpu

+1 −0
Original line number Diff line number Diff line
@@ -662,6 +662,7 @@ Description: Preferred MTE tag checking mode 


		================  ==============================================

		"sync"	  	  Prefer synchronous mode

		"asymm"	  	  Prefer asymmetric mode

		"async"	  	  Prefer asynchronous mode

		================  ==============================================

Documentation/admin-guide/kdump/vmcoreinfo.rst

+8 −0
Original line number Diff line number Diff line
@@ -494,6 +494,14 @@ architecture which is used to lookup the page-tables for the Virtual 
addresses in the higher VA range (refer to ARMv8 ARM document for

more details).



MODULES_VADDR|MODULES_END|VMALLOC_START|VMALLOC_END|VMEMMAP_START|VMEMMAP_END

-----------------------------------------------------------------------------



Used to get the correct ranges:

	MODULES_VADDR ~ MODULES_END-1 : Kernel module space.

	VMALLOC_START ~ VMALLOC_END-1 : vmalloc() / ioremap() space.

	VMEMMAP_START ~ VMEMMAP_END-1 : vmemmap region, used for struct page array.



arm

===

Documentation/arm64/booting.rst

+5 −5
Original line number Diff line number Diff line
@@ -10,9 +10,9 @@ This document is based on the ARM booting document by Russell King and 
is relevant to all public releases of the AArch64 Linux kernel.



The AArch64 exception model is made up of a number of exception levels

(EL0 - EL3), with EL0 and EL1 having a secure and a non-secure

counterpart.  EL2 is the hypervisor level and exists only in non-secure

mode. EL3 is the highest priority level and exists only in secure mode.

(EL0 - EL3), with EL0, EL1 and EL2 having a secure and a non-secure

counterpart.  EL2 is the hypervisor level, EL3 is the highest priority

level and exists only in secure mode. Both are architecturally optional.



For the purposes of this document, we will use the term `boot loader`

simply to define all software that executes on the CPU(s) before control
@@ -167,8 +167,8 @@ Before jumping into the kernel, the following conditions must be met: 


  All forms of interrupts must be masked in PSTATE.DAIF (Debug, SError,

  IRQ and FIQ).

  The CPU must be in either EL2 (RECOMMENDED in order to have access to

  the virtualisation extensions) or non-secure EL1.

  The CPU must be in non-secure state, either in EL2 (RECOMMENDED in order

  to have access to the virtualisation extensions), or in EL1.



- Caches, MMUs

Documentation/arm64/elf_hwcaps.rst

+5 −0
Original line number Diff line number Diff line
@@ -259,6 +259,11 @@ HWCAP2_RPRES 


    Functionality implied by ID_AA64ISAR2_EL1.RPRES == 0b0001.



HWCAP2_MTE3



    Functionality implied by ID_AA64PFR1_EL1.MTE == 0b0011, as described

    by Documentation/arm64/memory-tagging-extension.rst.



4. Unused AT_HWCAP bits

-----------------------

Documentation/arm64/memory-tagging-extension.rst

+44 −10
Original line number Diff line number Diff line
@@ -76,6 +76,9 @@ configurable behaviours: 
  with ``.si_code = SEGV_MTEAERR`` and ``.si_addr = 0`` (the faulting

  address is unknown).



- *Asymmetric* - Reads are handled as for synchronous mode while writes

  are handled as for asynchronous mode.



The user can select the above modes, per thread, using the

``prctl(PR_SET_TAGGED_ADDR_CTRL, flags, 0, 0, 0)`` system call where ``flags``

contains any number of the following values in the ``PR_MTE_TCF_MASK``
@@ -91,8 +94,9 @@ mode is specified, the program will run in that mode. If multiple 
modes are specified, the mode is selected as described in the "Per-CPU

preferred tag checking modes" section below.



The current tag check fault mode can be read using the

``prctl(PR_GET_TAGGED_ADDR_CTRL, 0, 0, 0, 0)`` system call.

The current tag check fault configuration can be read using the

``prctl(PR_GET_TAGGED_ADDR_CTRL, 0, 0, 0, 0)`` system call. If

multiple modes were requested then all will be reported.



Tag checking can also be disabled for a user thread by setting the

``PSTATE.TCO`` bit with ``MSR TCO, #1``.
@@ -139,18 +143,25 @@ tag checking mode as the CPU's preferred tag checking mode. 


The preferred tag checking mode for each CPU is controlled by

``/sys/devices/system/cpu/cpu<N>/mte_tcf_preferred``, to which a

privileged user may write the value ``async`` or ``sync``.  The default

preferred mode for each CPU is ``async``.

privileged user may write the value ``async``, ``sync`` or ``asymm``.  The

default preferred mode for each CPU is ``async``.



To allow a program to potentially run in the CPU's preferred tag

checking mode, the user program may set multiple tag check fault mode

bits in the ``flags`` argument to the ``prctl(PR_SET_TAGGED_ADDR_CTRL,

flags, 0, 0, 0)`` system call. If the CPU's preferred tag checking

mode is in the task's set of provided tag checking modes (this will

always be the case at present because the kernel only supports two

tag checking modes, but future kernels may support more modes), that

mode will be selected. Otherwise, one of the modes in the task's mode

set will be selected in a currently unspecified manner.

flags, 0, 0, 0)`` system call. If both synchronous and asynchronous

modes are requested then asymmetric mode may also be selected by the

kernel. If the CPU's preferred tag checking mode is in the task's set

of provided tag checking modes, that mode will be selected. Otherwise,

one of the modes in the task's mode will be selected by the kernel

from the task's mode set using the preference order:



	1. Asynchronous

	2. Asymmetric

	3. Synchronous



Note that there is no way for userspace to request multiple modes and

also disable asymmetric mode.



Initial process state

---------------------
@@ -213,6 +224,29 @@ address ABI control and MTE configuration of a process as per the 
Documentation/arm64/tagged-address-abi.rst and above. The corresponding

``regset`` is 1 element of 8 bytes (``sizeof(long))``).



Core dump support

-----------------



The allocation tags for user memory mapped with ``PROT_MTE`` are dumped

in the core file as additional ``PT_ARM_MEMTAG_MTE`` segments. The

program header for such segment is defined as:



:``p_type``: ``PT_ARM_MEMTAG_MTE``

:``p_flags``: 0

:``p_offset``: segment file offset

:``p_vaddr``: segment virtual address, same as the corresponding

  ``PT_LOAD`` segment

:``p_paddr``: 0

:``p_filesz``: segment size in file, calculated as ``p_mem_sz / 32``

  (two 4-bit tags cover 32 bytes of memory)

:``p_memsz``: segment size in memory, same as the corresponding

  ``PT_LOAD`` segment

:``p_align``: 0



The tags are stored in the core file at ``p_offset`` as two 4-bit tags

in a byte. With the tag granule of 16 bytes, a 4K page requires 128

bytes in the core file.



Example of correct usage

========================