€•      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ"/translations/zh_CN/arch/arm64/sve”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ"/translations/zh_TW/arch/arm64/sve”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ"/translations/it_IT/arch/arm64/sve”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ"/translations/ja_JP/arch/arm64/sve”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ"/translations/ko_KR/arch/arm64/sve”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ"/translations/sp_SP/arch/arm64/sve”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ3Scalable Vector Extension support for AArch64 Linux”h]”hŒ3Scalable Vector Extension support for AArch64 Linux”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒ</var/lib/git/docbuild/linux/Documentation/arch/arm64/sve.rst”h KubhŒ	paragraph”“”)”}”(hŒ)Author: Dave Martin <Dave.Martin@arm.com>”h]”(hŒAuthor: Dave Martin <”…””}”(hh¹hžhhŸNh NubhŒ	reference”“”)”}”(hŒDave.Martin@arm.com”h]”hŒDave.Martin@arm.com”…””}”(hhÃhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:Dave.Martin@arm.com”uh1hÁhh¹ubhŒ>”…””}”(hh¹hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒDate:   4 August 2017”h]”hŒDate:   4 August 2017”…””}”(hhÝhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒìThis document outlines briefly the interface provided to userspace by Linux in
order to support use of the ARM Scalable Vector Extension (SVE), including
interactions with Streaming SVE mode added by the Scalable Matrix Extension
(SME).”h]”hŒìThis document outlines briefly the interface provided to userspace by Linux in
order to support use of the ARM Scalable Vector Extension (SVE), including
interactions with Streaming SVE mode added by the Scalable Matrix Extension
(SME).”…””}”(hhëhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K	hh£hžhubh¸)”}”(hŒdThis is an outline of the most important features and issues only and not
intended to be exhaustive.”h]”hŒdThis is an outline of the most important features and issues only and not
intended to be exhaustive.”…””}”(hhùhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒÊThis document does not aim to describe the SVE architecture or programmer's
model.  To aid understanding, a minimal description of relevant programmer's
model features for SVE is included in Appendix A.”h]”hŒÎThis document does not aim to describe the SVE architecture or programmerâ€™s
model.  To aid understanding, a minimal description of relevant programmerâ€™s
model features for SVE is included in Appendix A.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒ1.  General”h]”hŒ1.  General”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h KubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒaSVE registers Z0..Z31, P0..P15 and FFR and the current vector length VL, are
tracked per-thread.
”h]”h¸)”}”(hŒ`SVE registers Z0..Z31, P0..P15 and FFR and the current vector length VL, are
tracked per-thread.”h]”hŒ`SVE registers Z0..Z31, P0..P15 and FFR and the current vector length VL, are
tracked per-thread.”…””}”(hj1  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj-  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubj,  )”}”(hŒÊIn streaming mode FFR is not accessible unless HWCAP2_SME_FA64 is present
in the system, when it is not supported and these interfaces are used to
access streaming mode FFR is read and written as zero.
”h]”h¸)”}”(hŒÉIn streaming mode FFR is not accessible unless HWCAP2_SME_FA64 is present
in the system, when it is not supported and these interfaces are used to
access streaming mode FFR is read and written as zero.”h]”hŒÉIn streaming mode FFR is not accessible unless HWCAP2_SME_FA64 is present
in the system, when it is not supported and these interfaces are used to
access streaming mode FFR is read and written as zero.”…””}”(hjI  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhjE  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubj,  )”}”(hX!  The presence of SVE is reported to userspace via HWCAP_SVE in the aux vector
AT_HWCAP entry.  Presence of this flag implies the presence of the SVE
instructions and registers, and the Linux-specific system interfaces
described in this document.  SVE is reported in /proc/cpuinfo as "sve".
”h]”h¸)”}”(hX   The presence of SVE is reported to userspace via HWCAP_SVE in the aux vector
AT_HWCAP entry.  Presence of this flag implies the presence of the SVE
instructions and registers, and the Linux-specific system interfaces
described in this document.  SVE is reported in /proc/cpuinfo as "sve".”h]”hX$  The presence of SVE is reported to userspace via HWCAP_SVE in the aux vector
AT_HWCAP entry.  Presence of this flag implies the presence of the SVE
instructions and registers, and the Linux-specific system interfaces
described in this document.  SVE is reported in /proc/cpuinfo as â€œsveâ€.”…””}”(hja  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K hj]  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubj,  )”}”(hXš  Support for the execution of SVE instructions in userspace can also be
detected by reading the CPU ID register ID_AA64PFR0_EL1 using an MRS
instruction, and checking that the value of the SVE field is nonzero. [3]

It does not guarantee the presence of the system interfaces described in the
following sections: software that needs to verify that those interfaces are
present must check for HWCAP_SVE instead.
”h]”(h¸)”}”(hŒÕSupport for the execution of SVE instructions in userspace can also be
detected by reading the CPU ID register ID_AA64PFR0_EL1 using an MRS
instruction, and checking that the value of the SVE field is nonzero. [3]”h]”hŒÕSupport for the execution of SVE instructions in userspace can also be
detected by reading the CPU ID register ID_AA64PFR0_EL1 using an MRS
instruction, and checking that the value of the SVE field is nonzero. [3]”…””}”(hjy  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K%hju  ubh¸)”}”(hŒÂIt does not guarantee the presence of the system interfaces described in the
following sections: software that needs to verify that those interfaces are
present must check for HWCAP_SVE instead.”h]”hŒÂIt does not guarantee the presence of the system interfaces described in the
following sections: software that needs to verify that those interfaces are
present must check for HWCAP_SVE instead.”…””}”(hj‡  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K)hju  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubj,  )”}”(hXa  On hardware that supports the SVE2 extensions, HWCAP2_SVE2 will also
be reported in the AT_HWCAP2 aux vector entry.  In addition to this,
optional extensions to SVE2 may be reported by the presence of:

      HWCAP2_SVE2
      HWCAP2_SVEAES
      HWCAP2_SVEPMULL
      HWCAP2_SVEBITPERM
      HWCAP2_SVESHA3
      HWCAP2_SVESM4
      HWCAP2_SVE2P1

This list may be extended over time as the SVE architecture evolves.

These extensions are also reported via the CPU ID register ID_AA64ZFR0_EL1,
which userspace can read using an MRS instruction.  See elf_hwcaps.txt and
cpu-feature-registers.txt for details.
”h]”(h¸)”}”(hŒÉOn hardware that supports the SVE2 extensions, HWCAP2_SVE2 will also
be reported in the AT_HWCAP2 aux vector entry.  In addition to this,
optional extensions to SVE2 may be reported by the presence of:”h]”hŒÉOn hardware that supports the SVE2 extensions, HWCAP2_SVE2 will also
be reported in the AT_HWCAP2 aux vector entry.  In addition to this,
optional extensions to SVE2 may be reported by the presence of:”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K-hj›  ubhŒblock_quote”“”)”}”(hŒgHWCAP2_SVE2
HWCAP2_SVEAES
HWCAP2_SVEPMULL
HWCAP2_SVEBITPERM
HWCAP2_SVESHA3
HWCAP2_SVESM4
HWCAP2_SVE2P1
”h]”h¸)”}”(hŒfHWCAP2_SVE2
HWCAP2_SVEAES
HWCAP2_SVEPMULL
HWCAP2_SVEBITPERM
HWCAP2_SVESHA3
HWCAP2_SVESM4
HWCAP2_SVE2P1”h]”hŒfHWCAP2_SVE2
HWCAP2_SVEAES
HWCAP2_SVEPMULL
HWCAP2_SVEBITPERM
HWCAP2_SVESHA3
HWCAP2_SVESM4
HWCAP2_SVE2P1”…””}”(hj³  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K1hj¯  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h K1hj›  ubh¸)”}”(hŒDThis list may be extended over time as the SVE architecture evolves.”h]”hŒDThis list may be extended over time as the SVE architecture evolves.”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K9hj›  ubh¸)”}”(hŒ½These extensions are also reported via the CPU ID register ID_AA64ZFR0_EL1,
which userspace can read using an MRS instruction.  See elf_hwcaps.txt and
cpu-feature-registers.txt for details.”h]”hŒ½These extensions are also reported via the CPU ID register ID_AA64ZFR0_EL1,
which userspace can read using an MRS instruction.  See elf_hwcaps.txt and
cpu-feature-registers.txt for details.”…””}”(hjÕ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K;hj›  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubj,  )”}”(hX+  On hardware that supports the SME extensions, HWCAP2_SME will also be
reported in the AT_HWCAP2 aux vector entry.  Among other things SME adds
streaming mode which provides a subset of the SVE feature set using a
separate SME vector length and the same Z/V registers.  See sme.rst
for more details.
”h]”h¸)”}”(hX*  On hardware that supports the SME extensions, HWCAP2_SME will also be
reported in the AT_HWCAP2 aux vector entry.  Among other things SME adds
streaming mode which provides a subset of the SVE feature set using a
separate SME vector length and the same Z/V registers.  See sme.rst
for more details.”h]”hX*  On hardware that supports the SME extensions, HWCAP2_SME will also be
reported in the AT_HWCAP2 aux vector entry.  Among other things SME adds
streaming mode which provides a subset of the SVE feature set using a
separate SME vector length and the same Z/V registers.  See sme.rst
for more details.”…””}”(hjí  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K?hjé  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubj,  )”}”(hX¾  Debuggers should restrict themselves to interacting with the target via the
NT_ARM_SVE regset.  The recommended way of detecting support for this regset
is to connect to a target process first and then attempt a
ptrace(PTRACE_GETREGSET, pid, NT_ARM_SVE, &iov).  Note that when SME is
present and streaming SVE mode is in use the FPSIMD subset of registers
will be read via NT_ARM_SVE and NT_ARM_SVE writes will exit streaming mode
in the target.
”h]”h¸)”}”(hX½  Debuggers should restrict themselves to interacting with the target via the
NT_ARM_SVE regset.  The recommended way of detecting support for this regset
is to connect to a target process first and then attempt a
ptrace(PTRACE_GETREGSET, pid, NT_ARM_SVE, &iov).  Note that when SME is
present and streaming SVE mode is in use the FPSIMD subset of registers
will be read via NT_ARM_SVE and NT_ARM_SVE writes will exit streaming mode
in the target.”h]”hX½  Debuggers should restrict themselves to interacting with the target via the
NT_ARM_SVE regset.  The recommended way of detecting support for this regset
is to connect to a target process first and then attempt a
ptrace(PTRACE_GETREGSET, pid, NT_ARM_SVE, &iov).  Note that when SME is
present and streaming SVE mode is in use the FPSIMD subset of registers
will be read via NT_ARM_SVE and NT_ARM_SVE writes will exit streaming mode
in the target.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KEhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubj,  )”}”(hXÏ  Whenever SVE scalable register values (Zn, Pn, FFR) are exchanged in memory
between userspace and the kernel, the register value is encoded in memory in
an endianness-invariant layout, with bits [(8 * i + 7) : (8 * i)] encoded at
byte offset i from the start of the memory representation.  This affects for
example the signal frame (struct sve_context) and ptrace interface
(struct user_sve_header) and associated data.

Beware that on big-endian systems this results in a different byte order than
for the FPSIMD V-registers, which are stored as single host-endian 128-bit
values, with bits [(127 - 8 * i) : (120 - 8 * i)] of the register encoded at
byte offset i.  (struct fpsimd_context, struct user_fpsimd_state).

”h]”(h¸)”}”(hX£  Whenever SVE scalable register values (Zn, Pn, FFR) are exchanged in memory
between userspace and the kernel, the register value is encoded in memory in
an endianness-invariant layout, with bits [(8 * i + 7) : (8 * i)] encoded at
byte offset i from the start of the memory representation.  This affects for
example the signal frame (struct sve_context) and ptrace interface
(struct user_sve_header) and associated data.”h]”hX£  Whenever SVE scalable register values (Zn, Pn, FFR) are exchanged in memory
between userspace and the kernel, the register value is encoded in memory in
an endianness-invariant layout, with bits [(8 * i + 7) : (8 * i)] encoded at
byte offset i from the start of the memory representation.  This affects for
example the signal frame (struct sve_context) and ptrace interface
(struct user_sve_header) and associated data.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KMhj  ubh¸)”}”(hX(  Beware that on big-endian systems this results in a different byte order than
for the FPSIMD V-registers, which are stored as single host-endian 128-bit
values, with bits [(127 - 8 * i) : (120 - 8 * i)] of the register encoded at
byte offset i.  (struct fpsimd_context, struct user_fpsimd_state).”h]”hX(  Beware that on big-endian systems this results in a different byte order than
for the FPSIMD V-registers, which are stored as single host-endian 128-bit
values, with bits [(127 - 8 * i) : (120 - 8 * i)] of the register encoded at
byte offset i.  (struct fpsimd_context, struct user_fpsimd_state).”…””}”(hj+  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KThj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj(  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j&  hŸh¶h Khj  hžhubeh}”(h]”Œgeneral”ah ]”h"]”Œ
1. general”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ2.  Vector length terminology”h]”hŒ2.  Vector length terminology”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjO  hžhhŸh¶h K[ubh¸)”}”(hŒMThe size of an SVE vector (Z) register is referred to as the "vector length".”h]”hŒQThe size of an SVE vector (Z) register is referred to as the â€œvector lengthâ€.”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K]hjO  hžhubh¸)”}”(hŒnTo avoid confusion about the units used to express vector length, the kernel
adopts the following conventions:”h]”hŒnTo avoid confusion about the units used to express vector length, the kernel
adopts the following conventions:”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K_hjO  hžhubj'  )”}”(hhh]”(j,  )”}”(hŒ3Vector length (VL) = size of a Z-register in bytes
”h]”h¸)”}”(hŒ2Vector length (VL) = size of a Z-register in bytes”h]”hŒ2Vector length (VL) = size of a Z-register in bytes”…””}”(hjƒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kbhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj|  hžhhŸh¶h Nubj,  )”}”(hŒBVector quadwords (VQ) = size of a Z-register in units of 128 bits
”h]”h¸)”}”(hŒAVector quadwords (VQ) = size of a Z-register in units of 128 bits”h]”hŒAVector quadwords (VQ) = size of a Z-register in units of 128 bits”…””}”(hj›  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kdhj—  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj|  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h KbhjO  hžhubh¸)”}”(hŒ(So, VL = 16 * VQ.)”h]”hŒ(So, VL = 16 * VQ.)”…””}”(hjµ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KfhjO  hžhubh¸)”}”(hX  The VQ convention is used where the underlying granularity is important, such
as in data structure definitions.  In most other situations, the VL convention
is used.  This is consistent with the meaning of the "VL" pseudo-register in
the SVE instruction set architecture.”h]”hX  The VQ convention is used where the underlying granularity is important, such
as in data structure definitions.  In most other situations, the VL convention
is used.  This is consistent with the meaning of the â€œVLâ€ pseudo-register in
the SVE instruction set architecture.”…””}”(hjÃ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KhhjO  hžhubeh}”(h]”Œvector-length-terminology”ah ]”h"]”Œ2. vector length terminology”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K[ubh¢)”}”(hhh]”(h§)”}”(hŒ3.  System call behaviour”h]”hŒ3.  System call behaviour”…””}”(hjÜ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÙ  hžhhŸh¶h Koubj'  )”}”(hhh]”(j,  )”}”(hŒ¿On syscall, V0..V31 are preserved (as without SVE).  Thus, bits [127:0] of
Z0..Z31 are preserved.  All other bits of Z0..Z31, and all of P0..P15 and FFR
become zero on return from a syscall.
”h]”h¸)”}”(hŒ¾On syscall, V0..V31 are preserved (as without SVE).  Thus, bits [127:0] of
Z0..Z31 are preserved.  All other bits of Z0..Z31, and all of P0..P15 and FFR
become zero on return from a syscall.”h]”hŒ¾On syscall, V0..V31 are preserved (as without SVE).  Thus, bits [127:0] of
Z0..Z31 are preserved.  All other bits of Z0..Z31, and all of P0..P15 and FFR
become zero on return from a syscall.”…””}”(hjñ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kqhjí  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjê  hžhhŸh¶h Nubj,  )”}”(hŒYThe SVE registers are not used to pass arguments to or receive results from
any syscall.
”h]”h¸)”}”(hŒXThe SVE registers are not used to pass arguments to or receive results from
any syscall.”h]”hŒXThe SVE registers are not used to pass arguments to or receive results from
any syscall.”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kuhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjê  hžhhŸh¶h Nubj,  )”}”(hX¿  All other SVE state of a thread, including the currently configured vector
length, the state of the PR_SVE_VL_INHERIT flag, and the deferred vector
length (if any), is preserved across all syscalls, subject to the specific
exceptions for execve() described in section 6.

In particular, on return from a fork() or clone(), the parent and new child
process or thread share identical SVE configuration, matching that of the
parent before the call.

”h]”(h¸)”}”(hX  All other SVE state of a thread, including the currently configured vector
length, the state of the PR_SVE_VL_INHERIT flag, and the deferred vector
length (if any), is preserved across all syscalls, subject to the specific
exceptions for execve() described in section 6.”h]”hX  All other SVE state of a thread, including the currently configured vector
length, the state of the PR_SVE_VL_INHERIT flag, and the deferred vector
length (if any), is preserved across all syscalls, subject to the specific
exceptions for execve() described in section 6.”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kxhj  ubh¸)”}”(hŒ­In particular, on return from a fork() or clone(), the parent and new child
process or thread share identical SVE configuration, matching that of the
parent before the call.”h]”hŒ­In particular, on return from a fork() or clone(), the parent and new child
process or thread share identical SVE configuration, matching that of the
parent before the call.”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K}hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjê  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h KqhjÙ  hžhubeh}”(h]”Œsystem-call-behaviour”ah ]”h"]”Œ3. system call behaviour”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Koubh¢)”}”(hhh]”(h§)”}”(hŒ4.  Signal handling”h]”hŒ4.  Signal handling”…””}”(hjT  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjQ  hžhhŸh¶h Kƒubj'  )”}”(hhh]”(j,  )”}”(hŒXA new signal frame record sve_context encodes the SVE registers on signal
delivery. [1]
”h]”h¸)”}”(hŒWA new signal frame record sve_context encodes the SVE registers on signal
delivery. [1]”h]”hŒWA new signal frame record sve_context encodes the SVE registers on signal
delivery. [1]”…””}”(hji  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K…hje  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubj,  )”}”(hŒÐThis record is supplementary to fpsimd_context.  The FPSR and FPCR registers
are only present in fpsimd_context.  For convenience, the content of V0..V31
is duplicated between sve_context and fpsimd_context.
”h]”h¸)”}”(hŒÏThis record is supplementary to fpsimd_context.  The FPSR and FPCR registers
are only present in fpsimd_context.  For convenience, the content of V0..V31
is duplicated between sve_context and fpsimd_context.”h]”hŒÏThis record is supplementary to fpsimd_context.  The FPSR and FPCR registers
are only present in fpsimd_context.  For convenience, the content of V0..V31
is duplicated between sve_context and fpsimd_context.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kˆhj}  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubj,  )”}”(hŒëThe record contains a flag field which includes a flag SVE_SIG_FLAG_SM which
if set indicates that the thread is in streaming mode and the vector length
and register data (if present) describe the streaming SVE data and vector
length.
”h]”h¸)”}”(hŒêThe record contains a flag field which includes a flag SVE_SIG_FLAG_SM which
if set indicates that the thread is in streaming mode and the vector length
and register data (if present) describe the streaming SVE data and vector
length.”h]”hŒêThe record contains a flag field which includes a flag SVE_SIG_FLAG_SM which
if set indicates that the thread is in streaming mode and the vector length
and register data (if present) describe the streaming SVE data and vector
length.”…””}”(hj™  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KŒhj•  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubj,  )”}”(hŒ~The signal frame record for SVE always contains basic metadata, in particular
the thread's vector length (in sve_context.vl).
”h]”h¸)”}”(hŒ}The signal frame record for SVE always contains basic metadata, in particular
the thread's vector length (in sve_context.vl).”h]”hŒThe signal frame record for SVE always contains basic metadata, in particular
the threadâ€™s vector length (in sve_context.vl).”…””}”(hj±  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K‘hj­  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubj,  )”}”(hŒòThe SVE registers may or may not be included in the record, depending on
whether the registers are live for the thread.  The registers are present if
and only if:
sve_context.head.size >= SVE_SIG_CONTEXT_SIZE(sve_vq_from_vl(sve_context.vl)).
”h]”h¸)”}”(hŒñThe SVE registers may or may not be included in the record, depending on
whether the registers are live for the thread.  The registers are present if
and only if:
sve_context.head.size >= SVE_SIG_CONTEXT_SIZE(sve_vq_from_vl(sve_context.vl)).”h]”hŒñThe SVE registers may or may not be included in the record, depending on
whether the registers are live for the thread.  The registers are present if
and only if:
sve_context.head.size >= SVE_SIG_CONTEXT_SIZE(sve_vq_from_vl(sve_context.vl)).”…””}”(hjÉ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K”hjÅ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubj,  )”}”(hŒ¥If the registers are present, the remainder of the record has a vl-dependent
size and layout.  Macros SVE_SIG_* are defined [1] to facilitate access to
the members.
”h]”h¸)”}”(hŒ¤If the registers are present, the remainder of the record has a vl-dependent
size and layout.  Macros SVE_SIG_* are defined [1] to facilitate access to
the members.”h]”hŒ¤If the registers are present, the remainder of the record has a vl-dependent
size and layout.  Macros SVE_SIG_* are defined [1] to facilitate access to
the members.”…””}”(hjá  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K™hjÝ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubj,  )”}”(hŒÇEach scalable register (Zn, Pn, FFR) is stored in an endianness-invariant
layout, with bits [(8 * i + 7) : (8 * i)] stored at byte offset i from the
start of the register's representation in memory.
”h]”h¸)”}”(hŒÆEach scalable register (Zn, Pn, FFR) is stored in an endianness-invariant
layout, with bits [(8 * i + 7) : (8 * i)] stored at byte offset i from the
start of the register's representation in memory.”h]”hŒÈEach scalable register (Zn, Pn, FFR) is stored in an endianness-invariant
layout, with bits [(8 * i + 7) : (8 * i)] stored at byte offset i from the
start of the registerâ€™s representation in memory.”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khjõ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubj,  )”}”(hX"  If the SVE context is too big to fit in sigcontext.__reserved[], then extra
space is allocated on the stack, an extra_context record is written in
__reserved[] referencing this space.  sve_context is then written in the
extra space.  Refer to [1] for further details about this mechanism.

”h]”h¸)”}”(hX   If the SVE context is too big to fit in sigcontext.__reserved[], then extra
space is allocated on the stack, an extra_context record is written in
__reserved[] referencing this space.  sve_context is then written in the
extra space.  Refer to [1] for further details about this mechanism.”h]”hX   If the SVE context is too big to fit in sigcontext.__reserved[], then extra
space is allocated on the stack, an extra_context record is written in
__reserved[] referencing this space.  sve_context is then written in the
extra space.  Refer to [1] for further details about this mechanism.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¡hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjb  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h K…hjQ  hžhubeh}”(h]”Œsignal-handling”ah ]”h"]”Œ4. signal handling”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kƒubh¢)”}”(hhh]”(h§)”}”(hŒ5.  Signal return”h]”hŒ5.  Signal return”…””}”(hj6  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj3  hžhhŸh¶h K¨ubh¸)”}”(hŒ%When returning from a signal handler:”h]”hŒ%When returning from a signal handler:”…””}”(hjD  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kªhj3  hžhubj'  )”}”(hhh]”(j,  )”}”(hŒàIf there is no sve_context record in the signal frame, or if the record is
present but contains no register data as described in the previous section,
then the SVE registers/bits become non-live and take unspecified values.
”h]”h¸)”}”(hŒßIf there is no sve_context record in the signal frame, or if the record is
present but contains no register data as described in the previous section,
then the SVE registers/bits become non-live and take unspecified values.”h]”hŒßIf there is no sve_context record in the signal frame, or if the record is
present but contains no register data as described in the previous section,
then the SVE registers/bits become non-live and take unspecified values.”…””}”(hjY  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¬hjU  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjR  hžhhŸh¶h Nubj,  )”}”(hXx  If sve_context is present in the signal frame and contains full register
data, the SVE registers become live and are populated with the specified
data.  However, for backward compatibility reasons, bits [127:0] of Z0..Z31
are always restored from the corresponding members of fpsimd_context.vregs[]
and not from sve_context.  The remaining bits are restored from sve_context.
”h]”h¸)”}”(hXw  If sve_context is present in the signal frame and contains full register
data, the SVE registers become live and are populated with the specified
data.  However, for backward compatibility reasons, bits [127:0] of Z0..Z31
are always restored from the corresponding members of fpsimd_context.vregs[]
and not from sve_context.  The remaining bits are restored from sve_context.”h]”hXw  If sve_context is present in the signal frame and contains full register
data, the SVE registers become live and are populated with the specified
data.  However, for backward compatibility reasons, bits [127:0] of Z0..Z31
are always restored from the corresponding members of fpsimd_context.vregs[]
and not from sve_context.  The remaining bits are restored from sve_context.”…””}”(hjq  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K°hjm  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjR  hžhhŸh¶h Nubj,  )”}”(hŒzInclusion of fpsimd_context in the signal frame remains mandatory,
irrespective of whether sve_context is present or not.
”h]”h¸)”}”(hŒyInclusion of fpsimd_context in the signal frame remains mandatory,
irrespective of whether sve_context is present or not.”h]”hŒyInclusion of fpsimd_context in the signal frame remains mandatory,
irrespective of whether sve_context is present or not.”…””}”(hj‰  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¶hj…  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjR  hžhhŸh¶h Nubj,  )”}”(hŒØThe vector length cannot be changed via signal return.  If sve_context.vl in
the signal frame does not match the current vector length, the signal return
attempt is treated as illegal, resulting in a forced SIGSEGV.
”h]”h¸)”}”(hŒ×The vector length cannot be changed via signal return.  If sve_context.vl in
the signal frame does not match the current vector length, the signal return
attempt is treated as illegal, resulting in a forced SIGSEGV.”h]”hŒ×The vector length cannot be changed via signal return.  If sve_context.vl in
the signal frame does not match the current vector length, the signal return
attempt is treated as illegal, resulting in a forced SIGSEGV.”…””}”(hj¡  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¹hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjR  hžhhŸh¶h Nubj,  )”}”(hŒýIt is permitted to enter or leave streaming mode by setting or clearing
the SVE_SIG_FLAG_SM flag but applications should take care to ensure that
when doing so sve_context.vl and any register data are appropriate for the
vector length in the new mode.

”h]”h¸)”}”(hŒûIt is permitted to enter or leave streaming mode by setting or clearing
the SVE_SIG_FLAG_SM flag but applications should take care to ensure that
when doing so sve_context.vl and any register data are appropriate for the
vector length in the new mode.”h]”hŒûIt is permitted to enter or leave streaming mode by setting or clearing
the SVE_SIG_FLAG_SM flag but applications should take care to ensure that
when doing so sve_context.vl and any register data are appropriate for the
vector length in the new mode.”…””}”(hj¹  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K½hjµ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjR  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h K¬hj3  hžhubeh}”(h]”Œsignal-return”ah ]”h"]”Œ5. signal return”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K¨ubh¢)”}”(hhh]”(h§)”}”(hŒ6.  prctl extensions”h]”hŒ6.  prctl extensions”…””}”(hjÞ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÛ  hžhhŸh¶h KÄubh¸)”}”(hŒSSome new prctl() calls are added to allow programs to manage the SVE vector
length:”h]”hŒSSome new prctl() calls are added to allow programs to manage the SVE vector
length:”…””}”(hjì  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÆhjÛ  hžhubh¸)”}”(hŒ'prctl(PR_SVE_SET_VL, unsigned long arg)”h]”hŒ'prctl(PR_SVE_SET_VL, unsigned long arg)”…””}”(hjú  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÉhjÛ  hžhubj®  )”}”(hXD	  Sets the vector length of the calling thread and related flags, where
arg == vl | flags.  Other threads of the calling process are unaffected.

vl is the desired vector length, where sve_vl_valid(vl) must be true.

flags:

    PR_SVE_VL_INHERIT

        Inherit the current vector length across execve().  Otherwise, the
        vector length is reset to the system default at execve().  (See
        Section 9.)

    PR_SVE_SET_VL_ONEXEC

        Defer the requested vector length change until the next execve()
        performed by this thread.

        The effect is equivalent to implicit execution of the following
        call immediately after the next execve() (if any) by the thread:

            prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC)

        This allows launching of a new program with a different vector
        length, while avoiding runtime side effects in the caller.


        Without PR_SVE_SET_VL_ONEXEC, the requested change takes effect
        immediately.


Return value: a nonnegative on success, or a negative value on error:
    EINVAL: SVE not supported, invalid vector length requested, or
        invalid flags.


On success:

* Either the calling thread's vector length or the deferred vector length
  to be applied at the next execve() by the thread (dependent on whether
  PR_SVE_SET_VL_ONEXEC is present in arg), is set to the largest value
  supported by the system that is less than or equal to vl.  If vl ==
  SVE_VL_MAX, the value set will be the largest value supported by the
  system.

* Any previously outstanding deferred vector length change in the calling
  thread is cancelled.

* The returned value describes the resulting configuration, encoded as for
  PR_SVE_GET_VL.  The vector length reported in this value is the new
  current vector length for this thread if PR_SVE_SET_VL_ONEXEC was not
  present in arg; otherwise, the reported vector length is the deferred
  vector length that will be applied at the next execve() by the calling
  thread.

* Changing the vector length causes all of P0..P15, FFR and all bits of
  Z0..Z31 except for Z0 bits [127:0] .. Z31 bits [127:0] to become
  unspecified.  Calling PR_SVE_SET_VL with vl equal to the thread's current
  vector length, or calling PR_SVE_SET_VL with the PR_SVE_SET_VL_ONEXEC
  flag, does not constitute a change to the vector length for this purpose.

”h]”(h¸)”}”(hŒŽSets the vector length of the calling thread and related flags, where
arg == vl | flags.  Other threads of the calling process are unaffected.”h]”hŒŽSets the vector length of the calling thread and related flags, where
arg == vl | flags.  Other threads of the calling process are unaffected.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KËhj  ubh¸)”}”(hŒEvl is the desired vector length, where sve_vl_valid(vl) must be true.”h]”hŒEvl is the desired vector length, where sve_vl_valid(vl) must be true.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÎhj  ubh¸)”}”(hŒflags:”h]”hŒflags:”…””}”(hj(  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÐhj  ubj®  )”}”(hXÈ  PR_SVE_VL_INHERIT

    Inherit the current vector length across execve().  Otherwise, the
    vector length is reset to the system default at execve().  (See
    Section 9.)

PR_SVE_SET_VL_ONEXEC

    Defer the requested vector length change until the next execve()
    performed by this thread.

    The effect is equivalent to implicit execution of the following
    call immediately after the next execve() (if any) by the thread:

        prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC)

    This allows launching of a new program with a different vector
    length, while avoiding runtime side effects in the caller.


    Without PR_SVE_SET_VL_ONEXEC, the requested change takes effect
    immediately.

”h]”(h¸)”}”(hŒPR_SVE_VL_INHERIT”h]”hŒPR_SVE_VL_INHERIT”…””}”(hj:  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÒhj6  ubj®  )”}”(hŒInherit the current vector length across execve().  Otherwise, the
vector length is reset to the system default at execve().  (See
Section 9.)
”h]”h¸)”}”(hŒŽInherit the current vector length across execve().  Otherwise, the
vector length is reset to the system default at execve().  (See
Section 9.)”h]”hŒŽInherit the current vector length across execve().  Otherwise, the
vector length is reset to the system default at execve().  (See
Section 9.)”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÔhjH  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h KÔhj6  ubh¸)”}”(hŒPR_SVE_SET_VL_ONEXEC”h]”hŒPR_SVE_SET_VL_ONEXEC”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KØhj6  ubj®  )”}”(hXß  Defer the requested vector length change until the next execve()
performed by this thread.

The effect is equivalent to implicit execution of the following
call immediately after the next execve() (if any) by the thread:

    prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC)

This allows launching of a new program with a different vector
length, while avoiding runtime side effects in the caller.


Without PR_SVE_SET_VL_ONEXEC, the requested change takes effect
immediately.

”h]”(h¸)”}”(hŒZDefer the requested vector length change until the next execve()
performed by this thread.”h]”hŒZDefer the requested vector length change until the next execve()
performed by this thread.”…””}”(hjr  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÚhjn  ubh¸)”}”(hŒ€The effect is equivalent to implicit execution of the following
call immediately after the next execve() (if any) by the thread:”h]”hŒ€The effect is equivalent to implicit execution of the following
call immediately after the next execve() (if any) by the thread:”…””}”(hj€  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KÝhjn  ubj®  )”}”(hŒ2prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC)
”h]”h¸)”}”(hŒ1prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC)”h]”hŒ1prctl(PR_SVE_SET_VL, arg & ~PR_SVE_SET_VL_ONEXEC)”…””}”(hj’  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KàhjŽ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h Kàhjn  ubh¸)”}”(hŒyThis allows launching of a new program with a different vector
length, while avoiding runtime side effects in the caller.”h]”hŒyThis allows launching of a new program with a different vector
length, while avoiding runtime side effects in the caller.”…””}”(hj¦  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kâhjn  ubh¸)”}”(hŒLWithout PR_SVE_SET_VL_ONEXEC, the requested change takes effect
immediately.”h]”hŒLWithout PR_SVE_SET_VL_ONEXEC, the requested change takes effect
immediately.”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kæhjn  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h KÚhj6  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h KÒhj  ubhŒdefinition_list”“”)”}”(hhh]”hŒdefinition_list_item”“”)”}”(hŒ™Return value: a nonnegative on success, or a negative value on error:
EINVAL: SVE not supported, invalid vector length requested, or
    invalid flags.

”h]”(hŒterm”“”)”}”(hŒEReturn value: a nonnegative on success, or a negative value on error:”h]”hŒEReturn value: a nonnegative on success, or a negative value on error:”…””}”(hjÛ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h KíhjÕ  ubhŒ
definition”“”)”}”(hhh]”jÏ  )”}”(hhh]”jÔ  )”}”(hŒOEINVAL: SVE not supported, invalid vector length requested, or
invalid flags.

”h]”(jÚ  )”}”(hŒ>EINVAL: SVE not supported, invalid vector length requested, or”h]”hŒ>EINVAL: SVE not supported, invalid vector length requested, or”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h Kíhjñ  ubjê  )”}”(hhh]”h¸)”}”(hŒinvalid flags.”h]”hŒinvalid flags.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kìhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hjñ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h Kíhjî  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÎ  hjë  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hjÕ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h KíhjÐ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÎ  hj  ubh¸)”}”(hŒOn success:”h]”hŒOn success:”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kïhj  ubj'  )”}”(hhh]”(j,  )”}”(hXe  Either the calling thread's vector length or the deferred vector length
to be applied at the next execve() by the thread (dependent on whether
PR_SVE_SET_VL_ONEXEC is present in arg), is set to the largest value
supported by the system that is less than or equal to vl.  If vl ==
SVE_VL_MAX, the value set will be the largest value supported by the
system.
”h]”h¸)”}”(hXd  Either the calling thread's vector length or the deferred vector length
to be applied at the next execve() by the thread (dependent on whether
PR_SVE_SET_VL_ONEXEC is present in arg), is set to the largest value
supported by the system that is less than or equal to vl.  If vl ==
SVE_VL_MAX, the value set will be the largest value supported by the
system.”h]”hXf  Either the calling threadâ€™s vector length or the deferred vector length
to be applied at the next execve() by the thread (dependent on whether
PR_SVE_SET_VL_ONEXEC is present in arg), is set to the largest value
supported by the system that is less than or equal to vl.  If vl ==
SVE_VL_MAX, the value set will be the largest value supported by the
system.”…””}”(hjM  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KñhjI  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjF  ubj,  )”}”(hŒ]Any previously outstanding deferred vector length change in the calling
thread is cancelled.
”h]”h¸)”}”(hŒ\Any previously outstanding deferred vector length change in the calling
thread is cancelled.”h]”hŒ\Any previously outstanding deferred vector length change in the calling
thread is cancelled.”…””}”(hje  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Køhja  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjF  ubj,  )”}”(hXh  The returned value describes the resulting configuration, encoded as for
PR_SVE_GET_VL.  The vector length reported in this value is the new
current vector length for this thread if PR_SVE_SET_VL_ONEXEC was not
present in arg; otherwise, the reported vector length is the deferred
vector length that will be applied at the next execve() by the calling
thread.
”h]”h¸)”}”(hXg  The returned value describes the resulting configuration, encoded as for
PR_SVE_GET_VL.  The vector length reported in this value is the new
current vector length for this thread if PR_SVE_SET_VL_ONEXEC was not
present in arg; otherwise, the reported vector length is the deferred
vector length that will be applied at the next execve() by the calling
thread.”h]”hXg  The returned value describes the resulting configuration, encoded as for
PR_SVE_GET_VL.  The vector length reported in this value is the new
current vector length for this thread if PR_SVE_SET_VL_ONEXEC was not
present in arg; otherwise, the reported vector length is the deferred
vector length that will be applied at the next execve() by the calling
thread.”…””}”(hj}  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kûhjy  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjF  ubj,  )”}”(hXb  Changing the vector length causes all of P0..P15, FFR and all bits of
Z0..Z31 except for Z0 bits [127:0] .. Z31 bits [127:0] to become
unspecified.  Calling PR_SVE_SET_VL with vl equal to the thread's current
vector length, or calling PR_SVE_SET_VL with the PR_SVE_SET_VL_ONEXEC
flag, does not constitute a change to the vector length for this purpose.

”h]”h¸)”}”(hX`  Changing the vector length causes all of P0..P15, FFR and all bits of
Z0..Z31 except for Z0 bits [127:0] .. Z31 bits [127:0] to become
unspecified.  Calling PR_SVE_SET_VL with vl equal to the thread's current
vector length, or calling PR_SVE_SET_VL with the PR_SVE_SET_VL_ONEXEC
flag, does not constitute a change to the vector length for this purpose.”h]”hXb  Changing the vector length causes all of P0..P15, FFR and all bits of
Z0..Z31 except for Z0 bits [127:0] .. Z31 bits [127:0] to become
unspecified.  Calling PR_SVE_SET_VL with vl equal to the threadâ€™s current
vector length, or calling PR_SVE_SET_VL with the PR_SVE_SET_VL_ONEXEC
flag, does not constitute a change to the vector length for this purpose.”…””}”(hj•  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhj‘  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjF  ubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h Kñhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h KËhjÛ  hžhubh¸)”}”(hŒprctl(PR_SVE_GET_VL)”h]”hŒprctl(PR_SVE_GET_VL)”…””}”(hjµ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M	hjÛ  hžhubj®  )”}”(hXD  Gets the vector length of the calling thread.

The following flag may be OR-ed into the result:

    PR_SVE_VL_INHERIT

        Vector length will be inherited across execve().

There is no way to determine whether there is an outstanding deferred
vector length change (which would only normally be the case between a
fork() or vfork() and the corresponding execve() in typical use).

To extract the vector length from the result, bitwise and it with
PR_SVE_VL_LEN_MASK.

Return value: a nonnegative value on success, or a negative value on error:
    EINVAL: SVE not supported.

”h]”(h¸)”}”(hŒ-Gets the vector length of the calling thread.”h]”hŒ-Gets the vector length of the calling thread.”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjÃ  ubh¸)”}”(hŒ0The following flag may be OR-ed into the result:”h]”hŒ0The following flag may be OR-ed into the result:”…””}”(hjÕ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjÃ  ubj®  )”}”(hŒHPR_SVE_VL_INHERIT

    Vector length will be inherited across execve().
”h]”(h¸)”}”(hŒPR_SVE_VL_INHERIT”h]”hŒPR_SVE_VL_INHERIT”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhjã  ubj®  )”}”(hŒ1Vector length will be inherited across execve().
”h]”h¸)”}”(hŒ0Vector length will be inherited across execve().”h]”hŒ0Vector length will be inherited across execve().”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhjõ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h Mhjã  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h MhjÃ  ubh¸)”}”(hŒÍThere is no way to determine whether there is an outstanding deferred
vector length change (which would only normally be the case between a
fork() or vfork() and the corresponding execve() in typical use).”h]”hŒÍThere is no way to determine whether there is an outstanding deferred
vector length change (which would only normally be the case between a
fork() or vfork() and the corresponding execve() in typical use).”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjÃ  ubh¸)”}”(hŒUTo extract the vector length from the result, bitwise and it with
PR_SVE_VL_LEN_MASK.”h]”hŒUTo extract the vector length from the result, bitwise and it with
PR_SVE_VL_LEN_MASK.”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjÃ  ubjÏ  )”}”(hhh]”jÔ  )”}”(hŒhReturn value: a nonnegative value on success, or a negative value on error:
EINVAL: SVE not supported.

”h]”(jÚ  )”}”(hŒKReturn value: a nonnegative value on success, or a negative value on error:”h]”hŒKReturn value: a nonnegative value on success, or a negative value on error:”…””}”(hj6  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h Mhj2  ubjê  )”}”(hhh]”h¸)”}”(hŒEINVAL: SVE not supported.”h]”hŒEINVAL: SVE not supported.”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjD  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hj2  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h Mhj/  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÎ  hjÃ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h MhjÛ  hžhubeh}”(h]”Œprctl-extensions”ah ]”h"]”Œ6. prctl extensions”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KÄubh¢)”}”(hhh]”(h§)”}”(hŒ7.  ptrace extensions”h]”hŒ7.  ptrace extensions”…””}”(hjx  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hju  hžhhŸh¶h Mubj'  )”}”(hhh]”j,  )”}”(hXÎ  New regsets NT_ARM_SVE and NT_ARM_SSVE are defined for use with
PTRACE_GETREGSET and PTRACE_SETREGSET. NT_ARM_SSVE describes the
streaming mode SVE registers and NT_ARM_SVE describes the
non-streaming mode SVE registers.

In this description a register set is referred to as being "live" when
the target is in the appropriate streaming or non-streaming mode and is
using data beyond the subset shared with the FPSIMD Vn registers.

Refer to [2] for definitions.
”h]”(h¸)”}”(hŒÜNew regsets NT_ARM_SVE and NT_ARM_SSVE are defined for use with
PTRACE_GETREGSET and PTRACE_SETREGSET. NT_ARM_SSVE describes the
streaming mode SVE registers and NT_ARM_SVE describes the
non-streaming mode SVE registers.”h]”hŒÜNew regsets NT_ARM_SVE and NT_ARM_SSVE are defined for use with
PTRACE_GETREGSET and PTRACE_SETREGSET. NT_ARM_SSVE describes the
streaming mode SVE registers and NT_ARM_SVE describes the
non-streaming mode SVE registers.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M!hj‰  ubh¸)”}”(hŒÐIn this description a register set is referred to as being "live" when
the target is in the appropriate streaming or non-streaming mode and is
using data beyond the subset shared with the FPSIMD Vn registers.”h]”hŒÔIn this description a register set is referred to as being â€œliveâ€ when
the target is in the appropriate streaming or non-streaming mode and is
using data beyond the subset shared with the FPSIMD Vn registers.”…””}”(hj›  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M&hj‰  ubh¸)”}”(hŒRefer to [2] for definitions.”h]”hŒRefer to [2] for definitions.”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M*hj‰  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj†  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h M!hju  hžhubh¸)”}”(hŒ?The regset data starts with struct user_sve_header, containing:”h]”hŒ?The regset data starts with struct user_sve_header, containing:”…””}”(hjÃ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M,hju  hžhubj®  )”}”(hXJ  size

    Size of the complete regset, in bytes.
    This depends on vl and possibly on other things in the future.

    If a call to PTRACE_GETREGSET requests less data than the value of
    size, the caller can allocate a larger buffer and retry in order to
    read the complete regset.

max_size

    Maximum size in bytes that the regset can grow to for the target
    thread.  The regset won't grow bigger than this even if the target
    thread changes its vector length etc.

vl

    Target thread's current vector length, in bytes.

max_vl

    Maximum possible vector length for the target thread.

flags

    at most one of

        SVE_PT_REGS_FPSIMD

            SVE registers are not live (GETREGSET) or are to be made
            non-live (SETREGSET).

            The payload is of type struct user_fpsimd_state, with the same
            meaning as for NT_PRFPREG, starting at offset
            SVE_PT_FPSIMD_OFFSET from the start of user_sve_header.

            Extra data might be appended in the future: the size of the
            payload should be obtained using SVE_PT_FPSIMD_SIZE(vq, flags).

            vq should be obtained using sve_vq_from_vl(vl).

            or

        SVE_PT_REGS_SVE

            SVE registers are live (GETREGSET) or are to be made live
            (SETREGSET).

            The payload contains the SVE register data, starting at offset
            SVE_PT_SVE_OFFSET from the start of user_sve_header, and with
            size SVE_PT_SVE_SIZE(vq, flags);

    ... OR-ed with zero or more of the following flags, which have the same
    meaning and behaviour as the corresponding PR_SET_VL_* flags:

        SVE_PT_VL_INHERIT

        SVE_PT_VL_ONEXEC (SETREGSET only).

    If neither FPSIMD nor SVE flags are provided then no register
    payload is available, this is only possible when SME is implemented.

”h]”(h¸)”}”(hŒsize”h]”hŒsize”…””}”(hjÕ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M.hjÑ  ubj®  )”}”(hX  Size of the complete regset, in bytes.
This depends on vl and possibly on other things in the future.

If a call to PTRACE_GETREGSET requests less data than the value of
size, the caller can allocate a larger buffer and retry in order to
read the complete regset.
”h]”(h¸)”}”(hŒeSize of the complete regset, in bytes.
This depends on vl and possibly on other things in the future.”h]”hŒeSize of the complete regset, in bytes.
This depends on vl and possibly on other things in the future.”…””}”(hjç  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M0hjã  ubh¸)”}”(hŒ If a call to PTRACE_GETREGSET requests less data than the value of
size, the caller can allocate a larger buffer and retry in order to
read the complete regset.”h]”hŒ If a call to PTRACE_GETREGSET requests less data than the value of
size, the caller can allocate a larger buffer and retry in order to
read the complete regset.”…””}”(hjõ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M3hjã  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h M0hjÑ  ubh¸)”}”(hŒmax_size”h]”hŒmax_size”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M7hjÑ  ubj®  )”}”(hŒªMaximum size in bytes that the regset can grow to for the target
thread.  The regset won't grow bigger than this even if the target
thread changes its vector length etc.
”h]”h¸)”}”(hŒ©Maximum size in bytes that the regset can grow to for the target
thread.  The regset won't grow bigger than this even if the target
thread changes its vector length etc.”h]”hŒ«Maximum size in bytes that the regset can grow to for the target
thread.  The regset wonâ€™t grow bigger than this even if the target
thread changes its vector length etc.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M9hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h M9hjÑ  ubh¸)”}”(hŒvl”h]”hŒvl”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M=hjÑ  ubj®  )”}”(hŒ1Target thread's current vector length, in bytes.
”h]”h¸)”}”(hŒ0Target thread's current vector length, in bytes.”h]”hŒ2Target threadâ€™s current vector length, in bytes.”…””}”(hjA  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M?hj=  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h M?hjÑ  ubh¸)”}”(hŒmax_vl”h]”hŒmax_vl”…””}”(hjU  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MAhjÑ  ubj®  )”}”(hŒ6Maximum possible vector length for the target thread.
”h]”h¸)”}”(hŒ5Maximum possible vector length for the target thread.”h]”hŒ5Maximum possible vector length for the target thread.”…””}”(hjg  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MChjc  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h MChjÑ  ubh¸)”}”(hŒflags”h]”hŒflags”…””}”(hj{  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MEhjÑ  ubj®  )”}”(hX†  at most one of

    SVE_PT_REGS_FPSIMD

        SVE registers are not live (GETREGSET) or are to be made
        non-live (SETREGSET).

        The payload is of type struct user_fpsimd_state, with the same
        meaning as for NT_PRFPREG, starting at offset
        SVE_PT_FPSIMD_OFFSET from the start of user_sve_header.

        Extra data might be appended in the future: the size of the
        payload should be obtained using SVE_PT_FPSIMD_SIZE(vq, flags).

        vq should be obtained using sve_vq_from_vl(vl).

        or

    SVE_PT_REGS_SVE

        SVE registers are live (GETREGSET) or are to be made live
        (SETREGSET).

        The payload contains the SVE register data, starting at offset
        SVE_PT_SVE_OFFSET from the start of user_sve_header, and with
        size SVE_PT_SVE_SIZE(vq, flags);

... OR-ed with zero or more of the following flags, which have the same
meaning and behaviour as the corresponding PR_SET_VL_* flags:

    SVE_PT_VL_INHERIT

    SVE_PT_VL_ONEXEC (SETREGSET only).

If neither FPSIMD nor SVE flags are provided then no register
payload is available, this is only possible when SME is implemented.

”h]”(h¸)”}”(hŒat most one of”h]”hŒat most one of”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MGhj‰  ubj®  )”}”(hXë  SVE_PT_REGS_FPSIMD

    SVE registers are not live (GETREGSET) or are to be made
    non-live (SETREGSET).

    The payload is of type struct user_fpsimd_state, with the same
    meaning as for NT_PRFPREG, starting at offset
    SVE_PT_FPSIMD_OFFSET from the start of user_sve_header.

    Extra data might be appended in the future: the size of the
    payload should be obtained using SVE_PT_FPSIMD_SIZE(vq, flags).

    vq should be obtained using sve_vq_from_vl(vl).

    or

SVE_PT_REGS_SVE

    SVE registers are live (GETREGSET) or are to be made live
    (SETREGSET).

    The payload contains the SVE register data, starting at offset
    SVE_PT_SVE_OFFSET from the start of user_sve_header, and with
    size SVE_PT_SVE_SIZE(vq, flags);
”h]”(h¸)”}”(hŒSVE_PT_REGS_FPSIMD”h]”hŒSVE_PT_REGS_FPSIMD”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MIhj›  ubj®  )”}”(hX§  SVE registers are not live (GETREGSET) or are to be made
non-live (SETREGSET).

The payload is of type struct user_fpsimd_state, with the same
meaning as for NT_PRFPREG, starting at offset
SVE_PT_FPSIMD_OFFSET from the start of user_sve_header.

Extra data might be appended in the future: the size of the
payload should be obtained using SVE_PT_FPSIMD_SIZE(vq, flags).

vq should be obtained using sve_vq_from_vl(vl).

or
”h]”(h¸)”}”(hŒNSVE registers are not live (GETREGSET) or are to be made
non-live (SETREGSET).”h]”hŒNSVE registers are not live (GETREGSET) or are to be made
non-live (SETREGSET).”…””}”(hj±  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MKhj­  ubh¸)”}”(hŒ¤The payload is of type struct user_fpsimd_state, with the same
meaning as for NT_PRFPREG, starting at offset
SVE_PT_FPSIMD_OFFSET from the start of user_sve_header.”h]”hŒ¤The payload is of type struct user_fpsimd_state, with the same
meaning as for NT_PRFPREG, starting at offset
SVE_PT_FPSIMD_OFFSET from the start of user_sve_header.”…””}”(hj¿  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MNhj­  ubh¸)”}”(hŒ{Extra data might be appended in the future: the size of the
payload should be obtained using SVE_PT_FPSIMD_SIZE(vq, flags).”h]”hŒ{Extra data might be appended in the future: the size of the
payload should be obtained using SVE_PT_FPSIMD_SIZE(vq, flags).”…””}”(hjÍ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MRhj­  ubh¸)”}”(hŒ/vq should be obtained using sve_vq_from_vl(vl).”h]”hŒ/vq should be obtained using sve_vq_from_vl(vl).”…””}”(hjÛ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MUhj­  ubh¸)”}”(hŒor”h]”hŒor”…””}”(hjé  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MWhj­  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h MKhj›  ubh¸)”}”(hŒSVE_PT_REGS_SVE”h]”hŒSVE_PT_REGS_SVE”…””}”(hjý  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MYhj›  ubj®  )”}”(hŒæSVE registers are live (GETREGSET) or are to be made live
(SETREGSET).

The payload contains the SVE register data, starting at offset
SVE_PT_SVE_OFFSET from the start of user_sve_header, and with
size SVE_PT_SVE_SIZE(vq, flags);
”h]”(h¸)”}”(hŒFSVE registers are live (GETREGSET) or are to be made live
(SETREGSET).”h]”hŒFSVE registers are live (GETREGSET) or are to be made live
(SETREGSET).”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M[hj	  ubh¸)”}”(hŒThe payload contains the SVE register data, starting at offset
SVE_PT_SVE_OFFSET from the start of user_sve_header, and with
size SVE_PT_SVE_SIZE(vq, flags);”h]”hŒThe payload contains the SVE register data, starting at offset
SVE_PT_SVE_OFFSET from the start of user_sve_header, and with
size SVE_PT_SVE_SIZE(vq, flags);”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M^hj	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h M[hj›  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h MIhj‰  ubh¸)”}”(hŒ…... OR-ed with zero or more of the following flags, which have the same
meaning and behaviour as the corresponding PR_SET_VL_* flags:”h]”hŒ…... OR-ed with zero or more of the following flags, which have the same
meaning and behaviour as the corresponding PR_SET_VL_* flags:”…””}”(hj7	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mbhj‰  ubj®  )”}”(hŒ6SVE_PT_VL_INHERIT

SVE_PT_VL_ONEXEC (SETREGSET only).
”h]”(h¸)”}”(hŒSVE_PT_VL_INHERIT”h]”hŒSVE_PT_VL_INHERIT”…””}”(hjI	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MehjE	  ubh¸)”}”(hŒ"SVE_PT_VL_ONEXEC (SETREGSET only).”h]”hŒ"SVE_PT_VL_ONEXEC (SETREGSET only).”…””}”(hjW	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MghjE	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h Mehj‰  ubh¸)”}”(hŒ‚If neither FPSIMD nor SVE flags are provided then no register
payload is available, this is only possible when SME is implemented.”h]”hŒ‚If neither FPSIMD nor SVE flags are provided then no register
payload is available, this is only possible when SME is implemented.”…””}”(hjk	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mihj‰  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h MGhjÑ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h M.hju  hžhubj'  )”}”(hhh]”(j,  )”}”(hX  The effects of changing the vector length and/or flags are equivalent to
those documented for PR_SVE_SET_VL.

The caller must make a further GETREGSET call if it needs to know what VL is
actually set by SETREGSET, unless is it known in advance that the requested
VL is supported.
”h]”(h¸)”}”(hŒlThe effects of changing the vector length and/or flags are equivalent to
those documented for PR_SVE_SET_VL.”h]”hŒlThe effects of changing the vector length and/or flags are equivalent to
those documented for PR_SVE_SET_VL.”…””}”(hjŒ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mmhjˆ	  ubh¸)”}”(hŒ©The caller must make a further GETREGSET call if it needs to know what VL is
actually set by SETREGSET, unless is it known in advance that the requested
VL is supported.”h]”hŒ©The caller must make a further GETREGSET call if it needs to know what VL is
actually set by SETREGSET, unless is it known in advance that the requested
VL is supported.”…””}”(hjš	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mphjˆ	  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hŒ«In the SVE_PT_REGS_SVE case, the size and layout of the payload depends on
the header fields.  The SVE_PT_SVE_*() macros are provided to facilitate
access to the members.
”h]”h¸)”}”(hŒªIn the SVE_PT_REGS_SVE case, the size and layout of the payload depends on
the header fields.  The SVE_PT_SVE_*() macros are provided to facilitate
access to the members.”h]”hŒªIn the SVE_PT_REGS_SVE case, the size and layout of the payload depends on
the header fields.  The SVE_PT_SVE_*() macros are provided to facilitate
access to the members.”…””}”(hj²	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mthj®	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hŒ°In either case, for SETREGSET it is permissible to omit the payload, in which
case only the vector length and flags are changed (along with any
consequences of those changes).
”h]”h¸)”}”(hŒ¯In either case, for SETREGSET it is permissible to omit the payload, in which
case only the vector length and flags are changed (along with any
consequences of those changes).”h]”hŒ¯In either case, for SETREGSET it is permissible to omit the payload, in which
case only the vector length and flags are changed (along with any
consequences of those changes).”…””}”(hjÊ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MxhjÆ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hŒìIn systems supporting SME when in streaming mode a GETREGSET for
NT_REG_SVE will return only the user_sve_header with no register data,
similarly a GETREGSET for NT_REG_SSVE will not return any register data
when not in streaming mode.
”h]”h¸)”}”(hŒëIn systems supporting SME when in streaming mode a GETREGSET for
NT_REG_SVE will return only the user_sve_header with no register data,
similarly a GETREGSET for NT_REG_SSVE will not return any register data
when not in streaming mode.”h]”hŒëIn systems supporting SME when in streaming mode a GETREGSET for
NT_REG_SVE will return only the user_sve_header with no register data,
similarly a GETREGSET for NT_REG_SSVE will not return any register data
when not in streaming mode.”…””}”(hjâ	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M|hjÞ	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hŒBA GETREGSET for NT_ARM_SSVE will never return SVE_PT_REGS_FPSIMD.
”h]”h¸)”}”(hŒAA GETREGSET for NT_ARM_SSVE will never return SVE_PT_REGS_FPSIMD.”h]”hŒAA GETREGSET for NT_ARM_SSVE will never return SVE_PT_REGS_FPSIMD.”…””}”(hjú	  hžhhŸNh Nubah}”(h]”•¤’      h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mhjö	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hXë  For SETREGSET, if an SVE_PT_REGS_SVE payload is present and the
requested VL is not supported, the effect will be the same as if the
payload were omitted, except that an EIO error is reported.  No
attempt is made to translate the payload data to the correct layout
for the vector length actually set.  The thread's FPSIMD state is
preserved, but the remaining bits of the SVE registers become
unspecified.  It is up to the caller to translate the payload layout
for the actual VL and retry.
”h]”h¸)”}”(hXê  For SETREGSET, if an SVE_PT_REGS_SVE payload is present and the
requested VL is not supported, the effect will be the same as if the
payload were omitted, except that an EIO error is reported.  No
attempt is made to translate the payload data to the correct layout
for the vector length actually set.  The thread's FPSIMD state is
preserved, but the remaining bits of the SVE registers become
unspecified.  It is up to the caller to translate the payload layout
for the actual VL and retry.”h]”hXì  For SETREGSET, if an SVE_PT_REGS_SVE payload is present and the
requested VL is not supported, the effect will be the same as if the
payload were omitted, except that an EIO error is reported.  No
attempt is made to translate the payload data to the correct layout
for the vector length actually set.  The threadâ€™s FPSIMD state is
preserved, but the remaining bits of the SVE registers become
unspecified.  It is up to the caller to translate the payload layout
for the actual VL and retry.”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mƒhj
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hX  Where SME is implemented it is not possible to GETREGSET the register
state for normal SVE when in streaming mode, nor the streaming mode
register state when in normal mode, regardless of the implementation defined
behaviour of the hardware for sharing data between the two modes.
”h]”h¸)”}”(hX  Where SME is implemented it is not possible to GETREGSET the register
state for normal SVE when in streaming mode, nor the streaming mode
register state when in normal mode, regardless of the implementation defined
behaviour of the hardware for sharing data between the two modes.”h]”hX  Where SME is implemented it is not possible to GETREGSET the register
state for normal SVE when in streaming mode, nor the streaming mode
register state when in normal mode, regardless of the implementation defined
behaviour of the hardware for sharing data between the two modes.”…””}”(hj*
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MŒhj&
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hŒ½Any SETREGSET of NT_ARM_SVE will exit streaming mode if the target was in
streaming mode and any SETREGSET of NT_ARM_SSVE will enter streaming mode
if the target was not in streaming mode.
”h]”h¸)”}”(hŒ¼Any SETREGSET of NT_ARM_SVE will exit streaming mode if the target was in
streaming mode and any SETREGSET of NT_ARM_SSVE will enter streaming mode
if the target was not in streaming mode.”h]”hŒ¼Any SETREGSET of NT_ARM_SVE will exit streaming mode if the target was in
streaming mode and any SETREGSET of NT_ARM_SSVE will enter streaming mode
if the target was not in streaming mode.”…””}”(hjB
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M‘hj>
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hŒ»If any register data is provided along with SVE_PT_VL_ONEXEC then the
registers data will be interpreted with the current vector length, not
the vector length configured for use on exec.
”h]”h¸)”}”(hŒºIf any register data is provided along with SVE_PT_VL_ONEXEC then the
registers data will be interpreted with the current vector length, not
the vector length configured for use on exec.”h]”hŒºIf any register data is provided along with SVE_PT_VL_ONEXEC then the
registers data will be interpreted with the current vector length, not
the vector length configured for use on exec.”…””}”(hjZ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M•hjV
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubj,  )”}”(hŒEThe effect of writing a partial, incomplete payload is unspecified.

”h]”h¸)”}”(hŒCThe effect of writing a partial, incomplete payload is unspecified.”h]”hŒCThe effect of writing a partial, incomplete payload is unspecified.”…””}”(hjr
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M™hjn
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj…	  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h Mmhju  hžhubeh}”(h]”Œptrace-extensions”ah ]”h"]”Œ7. ptrace extensions”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mubh¢)”}”(hhh]”(h§)”}”(hŒ8.  ELF coredump extensions”h]”hŒ8.  ELF coredump extensions”…””}”(hj—
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj”
  hžhhŸh¶h Mubj'  )”}”(hhh]”j,  )”}”(hX  NT_ARM_SVE and NT_ARM_SSVE notes will be added to each coredump for
each thread of the dumped process.  The contents will be equivalent to the
data that would have been read if a PTRACE_GETREGSET of the corresponding
type were executed for each thread when the coredump was generated.
”h]”h¸)”}”(hX  NT_ARM_SVE and NT_ARM_SSVE notes will be added to each coredump for
each thread of the dumped process.  The contents will be equivalent to the
data that would have been read if a PTRACE_GETREGSET of the corresponding
type were executed for each thread when the coredump was generated.”h]”hX  NT_ARM_SVE and NT_ARM_SSVE notes will be added to each coredump for
each thread of the dumped process.  The contents will be equivalent to the
data that would have been read if a PTRACE_GETREGSET of the corresponding
type were executed for each thread when the coredump was generated.”…””}”(hj¬
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MŸhj¨
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj¥
  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h MŸhj”
  hžhubeh}”(h]”Œelf-coredump-extensions”ah ]”h"]”Œ8. elf coredump extensions”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mubh¢)”}”(hhh]”(h§)”}”(hŒ 9.  System runtime configuration”h]”hŒ 9.  System runtime configuration”…””}”(hjÑ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÎ
  hžhhŸh¶h M¥ubj'  )”}”(hhh]”j,  )”}”(hŒÌTo mitigate the ABI impact of expansion of the signal frame, a policy
mechanism is provided for administrators, distro maintainers and developers
to set the default vector length for userspace processes:
”h]”h¸)”}”(hŒËTo mitigate the ABI impact of expansion of the signal frame, a policy
mechanism is provided for administrators, distro maintainers and developers
to set the default vector length for userspace processes:”h]”hŒËTo mitigate the ABI impact of expansion of the signal frame, a policy
mechanism is provided for administrators, distro maintainers and developers
to set the default vector length for userspace processes:”…””}”(hjæ
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M§hjâ
  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjß
  hžhhŸh¶h Nubah}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h M§hjÎ
  hžhubh¸)”}”(hŒ'/proc/sys/abi/sve_default_vector_length”h]”hŒ'/proc/sys/abi/sve_default_vector_length”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M«hjÎ
  hžhubj®  )”}”(hX.  Writing the text representation of an integer to this file sets the system
default vector length to the specified value rounded to a supported value
using the same rules as for setting vector length via PR_SVE_SET_VL.

The result can be determined by reopening the file and reading its
contents.

At boot, the default vector length is initially set to 64 or the maximum
supported vector length, whichever is smaller.  This determines the initial
vector length of the init process (PID 1).

Reading this file returns the current system default vector length.
”h]”(h¸)”}”(hŒÙWriting the text representation of an integer to this file sets the system
default vector length to the specified value rounded to a supported value
using the same rules as for setting vector length via PR_SVE_SET_VL.”h]”hŒÙWriting the text representation of an integer to this file sets the system
default vector length to the specified value rounded to a supported value
using the same rules as for setting vector length via PR_SVE_SET_VL.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M­hj  ubh¸)”}”(hŒLThe result can be determined by reopening the file and reading its
contents.”h]”hŒLThe result can be determined by reopening the file and reading its
contents.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M±hj  ubh¸)”}”(hŒ¿At boot, the default vector length is initially set to 64 or the maximum
supported vector length, whichever is smaller.  This determines the initial
vector length of the init process (PID 1).”h]”hŒ¿At boot, the default vector length is initially set to 64 or the maximum
supported vector length, whichever is smaller.  This determines the initial
vector length of the init process (PID 1).”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M´hj  ubh¸)”}”(hŒCReading this file returns the current system default vector length.”h]”hŒCReading this file returns the current system default vector length.”…””}”(hj<  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M¸hj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h M­hjÎ
  hžhubj'  )”}”(hhh]”(j,  )”}”(hXO  At every execve() call, the new vector length of the new process is set to
the system default vector length, unless

  * PR_SVE_VL_INHERIT (or equivalently SVE_PT_VL_INHERIT) is set for the
    calling thread, or

  * a deferred vector length change is pending, established via the
    PR_SVE_SET_VL_ONEXEC flag (or SVE_PT_VL_ONEXEC).
”h]”(h¸)”}”(hŒsAt every execve() call, the new vector length of the new process is set to
the system default vector length, unless”h]”hŒsAt every execve() call, the new vector length of the new process is set to
the system default vector length, unless”…””}”(hjW  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MºhjS  ubj®  )”}”(hŒÒ* PR_SVE_VL_INHERIT (or equivalently SVE_PT_VL_INHERIT) is set for the
  calling thread, or

* a deferred vector length change is pending, established via the
  PR_SVE_SET_VL_ONEXEC flag (or SVE_PT_VL_ONEXEC).
”h]”j'  )”}”(hhh]”(j,  )”}”(hŒXPR_SVE_VL_INHERIT (or equivalently SVE_PT_VL_INHERIT) is set for the
calling thread, or
”h]”h¸)”}”(hŒWPR_SVE_VL_INHERIT (or equivalently SVE_PT_VL_INHERIT) is set for the
calling thread, or”h]”hŒWPR_SVE_VL_INHERIT (or equivalently SVE_PT_VL_INHERIT) is set for the
calling thread, or”…””}”(hjp  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M½hjl  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hji  ubj,  )”}”(hŒqa deferred vector length change is pending, established via the
PR_SVE_SET_VL_ONEXEC flag (or SVE_PT_VL_ONEXEC).
”h]”h¸)”}”(hŒpa deferred vector length change is pending, established via the
PR_SVE_SET_VL_ONEXEC flag (or SVE_PT_VL_ONEXEC).”h]”hŒpa deferred vector length change is pending, established via the
PR_SVE_SET_VL_ONEXEC flag (or SVE_PT_VL_ONEXEC).”…””}”(hjˆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÀhj„  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hji  ubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h M½hje  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j­  hŸh¶h M½hjS  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjP  hžhhŸh¶h Nubj,  )”}”(hŒ”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.
”h]”h¸)”}”(hŒ“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.”h]”hŒ“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.”…””}”(hj²  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÃhj®  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjP  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h MºhjÎ
  hžhubeh}”(h]”Œsystem-runtime-configuration”ah ]”h"]”Œ9. system runtime configuration”ah$]”h&]”uh1h¡hh£hžhhŸh¶h M¥ubh¢)”}”(hhh]”(h§)”}”(hŒ10.  Perf extensions”h]”hŒ10.  Perf extensions”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÔ  hžhhŸh¶h MÇubj'  )”}”(hhh]”(j,  )”}”(hŒÂ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.
”h]”h¸)”}”(hŒÁ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.”h]”hŒÁ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.”…””}”(hjì  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÉhjè  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjå  hžhhŸh¶h Nubj,  )”}”(hŒUIts value is equivalent to the current SVE vector length (VL) in bits divided
by 64.
”h]”h¸)”}”(hŒTIts value is equivalent to the current SVE vector length (VL) in bits divided
by 64.”h]”hŒTIts value is equivalent to the current SVE vector length (VL) in bits divided
by 64.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÍhj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjå  hžhhŸh¶h Nubj,  )”}”(hŒŠ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.
”h]”h¸)”}”(hŒ‰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.”h]”hŒ‰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.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÐhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjå  hžhhŸh¶h Nubj,  )”}”(hŒ^The value is the current value at the time the sample was taken, and it can
change over time.
”h]”h¸)”}”(hŒ]The value is the current value at the time the sample was taken, and it can
change over time.”h]”hŒ]The value is the current value at the time the sample was taken, and it can
change over time.”…””}”(hj4  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÓhj0  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjå  hžhhŸh¶h Nubj,  )”}”(hŒsIf the system doesn't support SVE when perf_event_open is called with these
settings, the event will fail to open.
”h]”h¸)”}”(hŒrIf the system doesn't support SVE when perf_event_open is called with these
settings, the event will fail to open.”h]”hŒtIf the system doesnâ€™t support SVE when perf_event_open is called with these
settings, the event will fail to open.”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÖhjH  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjå  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h MÉhjÔ  hžhubh¢)”}”(hhh]”(h§)”}”(hŒ1Appendix A.  SVE programmer's model (informative)”h]”hŒ3Appendix A.  SVE programmerâ€™s model (informative)”…””}”(hji  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjf  hžhhŸh¶h MÚubh¸)”}”(hŒŽThis section provides a minimal description of the additions made by SVE to the
ARMv8-A programmer's model that are relevant to this document.”h]”hŒThis section provides a minimal description of the additions made by SVE to the
ARMv8-A programmerâ€™s model that are relevant to this document.”…””}”(hjw  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MÜhjf  hžhubh¸)”}”(hŒyNote: This section is for information only and not intended to be complete or
to replace any architectural specification.”h]”hŒyNote: This section is for information only and not intended to be complete or
to replace any architectural specification.”…””}”(hj…  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mßhjf  hžhubeh}”(h]”Œ-appendix-a-sve-programmer-s-model-informative”ah ]”h"]”Œ0appendix a. sve programmer's model (informative)”ah$]”h&]”uh1h¡hjÔ  hžhhŸh¶h MÚubeh}”(h]”Œperf-extensions”ah ]”h"]”Œ10. perf extensions”ah$]”h&]”uh1h¡hh£hžhhŸh¶h MÇubh¢)”}”(hhh]”(h§)”}”(hŒA.1.  Registers”h]”hŒA.1.  Registers”…””}”(hj¦  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj£  hžhhŸh¶h Mãubh¸)”}”(hŒ%In A64 state, SVE adds the following:”h]”hŒ%In A64 state, SVE adds the following:”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Måhj£  hžhubj'  )”}”(hhh]”(j,  )”}”(hŒÒ32 8VL-bit vector registers Z0..Z31
For each Zn, Zn bits [127:0] alias the ARMv8-A vector register Vn.

A register write using a Vn register name zeros all bits of the corresponding
Zn except for bits [127:0].
”h]”(h¸)”}”(hŒf32 8VL-bit vector registers Z0..Z31
For each Zn, Zn bits [127:0] alias the ARMv8-A vector register Vn.”h]”hŒf32 8VL-bit vector registers Z0..Z31
For each Zn, Zn bits [127:0] alias the ARMv8-A vector register Vn.”…””}”(hjÉ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MçhjÅ  ubh¸)”}”(hŒiA register write using a Vn register name zeros all bits of the corresponding
Zn except for bits [127:0].”h]”hŒiA register write using a Vn register name zeros all bits of the corresponding
Zn except for bits [127:0].”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MêhjÅ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjÂ  hžhhŸh¶h Nubj,  )”}”(hŒ&16 VL-bit predicate registers P0..P15
”h]”h¸)”}”(hŒ%16 VL-bit predicate registers P0..P15”h]”hŒ%16 VL-bit predicate registers P0..P15”…””}”(hjï  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Míhjë  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjÂ  hžhhŸh¶h Nubj,  )”}”(hŒM1 VL-bit special-purpose predicate register FFR (the "first-fault register")
”h]”h¸)”}”(hŒL1 VL-bit special-purpose predicate register FFR (the "first-fault register")”h]”hŒP1 VL-bit special-purpose predicate register FFR (the â€œfirst-fault registerâ€)”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mïhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjÂ  hžhhŸh¶h Nubj,  )”}”(hŒða VL "pseudo-register" that determines the size of each vector register

The SVE instruction set architecture provides no way to write VL directly.
Instead, it can be modified only by EL1 and above, by writing appropriate
system registers.
”h]”(h¸)”}”(hŒGa VL "pseudo-register" that determines the size of each vector register”h]”hŒKa VL â€œpseudo-registerâ€ that determines the size of each vector register”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mñhj  ubh¸)”}”(hŒ¦The SVE instruction set architecture provides no way to write VL directly.
Instead, it can be modified only by EL1 and above, by writing appropriate
system registers.”h]”hŒ¦The SVE instruction set architecture provides no way to write VL directly.
Instead, it can be modified only by EL1 and above, by writing appropriate
system registers.”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Móhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjÂ  hžhhŸh¶h Nubj,  )”}”(hŒuThe value of VL can be configured at runtime by EL1 and above:
16 <= VL <= VLmax, where VL must be a multiple of 16.
”h]”h¸)”}”(hŒtThe value of VL can be configured at runtime by EL1 and above:
16 <= VL <= VLmax, where VL must be a multiple of 16.”h]”hŒtThe value of VL can be configured at runtime by EL1 and above:
16 <= VL <= VLmax, where VL must be a multiple of 16.”…””}”(hjE  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M÷hjA  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjÂ  hžhhŸh¶h Nubj,  )”}”(hŒ³The maximum vector length is determined by the hardware:
16 <= VLmax <= 256.

(The SVE architecture specifies 256, but permits future architecture
revisions to raise this limit.)
”h]”(h¸)”}”(hŒLThe maximum vector length is determined by the hardware:
16 <= VLmax <= 256.”h]”hŒLThe maximum vector length is determined by the hardware:
16 <= VLmax <= 256.”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MúhjY  ubh¸)”}”(hŒd(The SVE architecture specifies 256, but permits future architecture
revisions to raise this limit.)”h]”hŒd(The SVE architecture specifies 256, but permits future architecture
revisions to raise this limit.)”…””}”(hjk  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MýhjY  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjÂ  hžhhŸh¶h Nubj,  )”}”(hXZ  FPSR and FPCR are retained from ARMv8-A, and interact with SVE floating-point
operations in a similar way to the way in which they interact with ARMv8
floating-point operations::

       8VL-1                       128               0  bit index
      +----          ////            -----------------+
   Z0 |                               :       V0      |
    :                                          :
   Z7 |                               :       V7      |
   Z8 |                               :     * V8      |
    :                                       :  :
  Z15 |                               :     *V15      |
  Z16 |                               :      V16      |
    :                                          :
  Z31 |                               :      V31      |
      +----          ////            -----------------+
                                               31    0
       VL-1                  0                +-------+
      +----       ////      --+          FPSR |       |
   P0 |                       |               +-------+
    : |                       |         *FPCR |       |
  P15 |                       |               +-------+
      +----       ////      --+
  FFR |                       |               +-----+
      +----       ////      --+            VL |     |
                                              +-----+
”h]”(h¸)”}”(hŒ²FPSR and FPCR are retained from ARMv8-A, and interact with SVE floating-point
operations in a similar way to the way in which they interact with ARMv8
floating-point operations::”h]”hŒ±FPSR and FPCR are retained from ARMv8-A, and interact with SVE floating-point
operations in a similar way to the way in which they interact with ARMv8
floating-point operations:”…””}”(hjƒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M hj  ubhŒliteral_block”“”)”}”(hXy       8VL-1                       128               0  bit index
    +----          ////            -----------------+
 Z0 |                               :       V0      |
  :                                          :
 Z7 |                               :       V7      |
 Z8 |                               :     * V8      |
  :                                       :  :
Z15 |                               :     *V15      |
Z16 |                               :      V16      |
  :                                          :
Z31 |                               :      V31      |
    +----          ////            -----------------+
                                             31    0
     VL-1                  0                +-------+
    +----       ////      --+          FPSR |       |
 P0 |                       |               +-------+
  : |                       |         *FPCR |       |
P15 |                       |               +-------+
    +----       ////      --+
FFR |                       |               +-----+
    +----       ////      --+            VL |     |
                                            +-----+”h]”hXy       8VL-1                       128               0  bit index
    +----          ////            -----------------+
 Z0 |                               :       V0      |
  :                                          :
 Z7 |                               :       V7      |
 Z8 |                               :     * V8      |
  :                                       :  :
Z15 |                               :     *V15      |
Z16 |                               :      V16      |
  :                                          :
Z31 |                               :      V31      |
    +----          ////            -----------------+
                                             31    0
     VL-1                  0                +-------+
    +----       ////      --+          FPSR |       |
 P0 |                       |               +-------+
  : |                       |         *FPCR |       |
P15 |                       |               +-------+
    +----       ////      --+
FFR |                       |               +-----+
    +----       ////      --+            VL |     |
                                            +-----+”…””}”hj“  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j‘  hŸh¶h Mhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hjÂ  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h Mçhj£  hžhubjÏ  )”}”(hhh]”jÔ  )”}”(hŒŒ(*) callee-save:
This only applies to bits [63:0] of Z-/V-registers.
FPCR contains callee-save and caller-save bits.  See [4] for details.

”h]”(jÚ  )”}”(hŒ(*) callee-save:”h]”hŒ(*) callee-save:”…””}”(hj¶  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h Mhj²  ubjê  )”}”(hhh]”h¸)”}”(hŒyThis only applies to bits [63:0] of Z-/V-registers.
FPCR contains callee-save and caller-save bits.  See [4] for details.”h]”hŒyThis only applies to bits [63:0] of Z-/V-registers.
FPCR contains callee-save and caller-save bits.  See [4] for details.”…””}”(hjÇ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MhjÄ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hj²  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h Mhj¯  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÎ  hj£  hžhhŸh¶h Nubeh}”(h]”Œa-1-registers”ah ]”h"]”Œa.1. registers”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Mãubh¢)”}”(hhh]”(h§)”}”(hŒA.2.  Procedure call standard”h]”hŒA.2.  Procedure call standard”…””}”(hjò  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjï  hžhhŸh¶h M!ubh¸)”}”(hŒrThe ARMv8-A base procedure call standard is extended as follows with respect to
the additional SVE register state:”h]”hŒrThe ARMv8-A base procedure call standard is extended as follows with respect to
the additional SVE register state:”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M#hjï  hžhubj'  )”}”(hhh]”(j,  )”}”(hŒHAll SVE register bits that are not shared with FP/SIMD are caller-save.
”h]”h¸)”}”(hŒGAll SVE register bits that are not shared with FP/SIMD are caller-save.”h]”hŒGAll SVE register bits that are not shared with FP/SIMD are caller-save.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M&hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj  hžhhŸh¶h Nubj,  )”}”(hŒ­Z8 bits [63:0] .. Z15 bits [63:0] are callee-save.

This follows from the way these bits are mapped to V8..V15, which are caller-
save in the base procedure call standard.

”h]”(h¸)”}”(hŒ2Z8 bits [63:0] .. Z15 bits [63:0] are callee-save.”h]”hŒ2Z8 bits [63:0] .. Z15 bits [63:0] are callee-save.”…””}”(hj-  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M(hj)  ubh¸)”}”(hŒwThis follows from the way these bits are mapped to V8..V15, which are caller-
save in the base procedure call standard.”h]”hŒwThis follows from the way these bits are mapped to V8..V15, which are caller-
save in the base procedure call standard.”…””}”(hj;  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M*hj)  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h M&hjï  hžhubh¢)”}”(hhh]”(h§)”}”(hŒ/Appendix B.  ARMv8-A FP/SIMD programmer's model”h]”hŒ1Appendix B.  ARMv8-A FP/SIMD programmerâ€™s model”…””}”(hjX  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjU  hžhhŸh¶h M/ubh¸)”}”(hŒyNote: This section is for information only and not intended to be complete or
to replace any architectural specification.”h]”hŒyNote: This section is for information only and not intended to be complete or
to replace any architectural specification.”…””}”(hjf  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M1hjU  hžhubh¸)”}”(hŒ"Refer to [4] for more information.”h]”hŒ"Refer to [4] for more information.”…””}”(hjt  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M4hjU  hžhubh¸)”}”(hŒCARMv8-A defines the following floating-point / SIMD register state:”h]”hŒCARMv8-A defines the following floating-point / SIMD register state:”…””}”(hj‚  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M6hjU  hžhubj'  )”}”(hhh]”(j,  )”}”(hŒ#32 128-bit vector registers V0..V31”h]”h¸)”}”(hj•  h]”hŒ#32 128-bit vector registers V0..V31”…””}”(hj—  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M8hj“  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj  hžhhŸh¶h Nubj,  )”}”(hŒ-2 32-bit status/control registers FPSR, FPCR
”h]”h¸)”}”(hŒ,2 32-bit status/control registers FPSR, FPCR”h]”hŒ,2 32-bit status/control registers FPSR, FPCR”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M9hjª  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j+  hj  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jE  jF  uh1j&  hŸh¶h M8hjU  hžhubj’  )”}”(hX§        127           0  bit index
     +---------------+
  V0 |               |
   : :               :
  V7 |               |
* V8 |               |
:  : :               :
*V15 |               |
 V16 |               |
   : :               :
 V31 |               |
     +---------------+

              31    0
             +-------+
        FPSR |       |
             +-------+
       *FPCR |       |
             +-------+”h]”hX§        127           0  bit index
     +---------------+
  V0 |               |
   : :               :
  V7 |               |
* V8 |               |
:  : :               :
*V15 |               |
 V16 |               |
   : :               :
 V31 |               |
     +---------------+

              31    0
             +-------+
        FPSR |       |
             +-------+
       *FPCR |       |
             +-------+”…””}”hjÈ  sbah}”(h]”h ]”h"]”h$]”h&]”j¡  j¢  uh1j‘  hŸh¶h M=hjU  hžhubjÏ  )”}”(hhh]”jÔ  )”}”(hŒ€(*) callee-save:
This only applies to bits [63:0] of V-registers.
FPCR contains a mixture of callee-save and caller-save bits.

”h]”(jÚ  )”}”(hŒ(*) callee-save:”h]”hŒ(*) callee-save:”…””}”(hjÝ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h MThjÙ  ubjê  )”}”(hhh]”h¸)”}”(hŒmThis only applies to bits [63:0] of V-registers.
FPCR contains a mixture of callee-save and caller-save bits.”h]”hŒmThis only applies to bits [63:0] of V-registers.
FPCR contains a mixture of callee-save and caller-save bits.”…””}”(hjî  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MRhjë  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hjÙ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h MThjÖ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÎ  hjU  hžhhŸh¶h Nubeh}”(h]”Œ-appendix-b-armv8-a-fp-simd-programmer-s-model”ah ]”h"]”Œ.appendix b. armv8-a fp/simd programmer's model”ah$]”h&]”uh1h¡hjï  hžhhŸh¶h M/ubh¢)”}”(hhh]”(h§)”}”(hŒ
References”h]”hŒ
References”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h MWubjÏ  )”}”(hhh]”(jÔ  )”}”(hŒR[1] arch/arm64/include/uapi/asm/sigcontext.h
AArch64 Linux signal ABI definitions
”h]”(jÚ  )”}”(hŒ,[1] arch/arm64/include/uapi/asm/sigcontext.h”h]”hŒ,[1] arch/arm64/include/uapi/asm/sigcontext.h”…””}”(hj.  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h MZhj*  ubjê  )”}”(hhh]”h¸)”}”(hŒ$AArch64 Linux signal ABI definitions”h]”hŒ$AArch64 Linux signal ABI definitions”…””}”(hj?  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h MZhj<  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hj*  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h MZhj'  ubjÔ  )”}”(hŒN[2] arch/arm64/include/uapi/asm/ptrace.h
AArch64 Linux ptrace ABI definitions
”h]”(jÚ  )”}”(hŒ([2] arch/arm64/include/uapi/asm/ptrace.h”h]”hŒ([2] arch/arm64/include/uapi/asm/ptrace.h”…””}”(hj]  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h M]hjY  ubjê  )”}”(hhh]”h¸)”}”(hŒ$AArch64 Linux ptrace ABI definitions”h]”hŒ$AArch64 Linux ptrace ABI definitions”…””}”(hjn  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M]hjk  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hjY  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h M]hj'  hžhubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÎ  hj  hžhhŸh¶h Nubh¸)”}”(hŒ6[3] Documentation/arch/arm64/cpu-feature-registers.rst”h]”hŒ6[3] Documentation/arch/arm64/cpu-feature-registers.rst”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h M_hj  hžhubjÏ  )”}”(hhh]”jÔ  )”}”(hŒô[4] ARM IHI0055C
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)
”h]”(jÚ  )”}”(hŒ[4] ARM IHI0055C”h]”hŒ[4] ARM IHI0055C”…””}”(hj£  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÙ  hŸh¶h MdhjŸ  ubjê  )”}”(hhh]”h¸)”}”(hŒâ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)”h]”(hÂ)”}”(hŒShttp://infocenter.arm.com/help/topic/com.arm.doc.ihi0055c/IHI0055C_beta_aapcs64.pdf”h]”hŒShttp://infocenter.arm.com/help/topic/com.arm.doc.ihi0055c/IHI0055C_beta_aapcs64.pdf”…””}”(hj¸  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jº  uh1hÁhj´  ubhŒ
”…””}”(hj´  hžhhŸNh NubhÂ)”}”(hŒLhttp://infocenter.arm.com/help/topic/com.arm.doc.subset.swdev.abi/index.html”h]”hŒLhttp://infocenter.arm.com/help/topic/com.arm.doc.subset.swdev.abi/index.html”…””}”(hjË  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÍ  uh1hÁhj´  ubhŒB
Procedure Call Standard for the ARM 64-bit Architecture (AArch64)”…””}”(hj´  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mbhj±  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jé  hjŸ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jÓ  hŸh¶h Mdhjœ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÎ  hj  hžhhŸh¶h Nubh¸)”}”(hŒL[5] https://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst”h]”(hŒ[5] ”…””}”(hjö  hžhhŸNh NubhÂ)”}”(hŒHhttps://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst”h]”hŒHhttps://github.com/ARM-software/abi-aa/blob/main/aadwarf64/aadwarf64.rst”…””}”(hjþ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j   uh1hÁhjö  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Mfhj  hžhubeh}”(h]”Œ
references”ah ]”h"]”Œ
references”ah$]”h&]”uh1h¡hjï  hžhhŸh¶h MWubeh}”(h]”Œa-2-procedure-call-standard”ah ]”h"]”Œa.2. procedure call standard”ah$]”h&]”uh1h¡hh£hžhhŸh¶h M!ubeh}”(h]”Œ3scalable-vector-extension-support-for-aarch64-linux”ah ]”h"]”Œ3scalable vector extension support for aarch64 linux”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jN  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j(  j%  jL  jI  jÖ  jÓ  jN  jK  j0  j-  jØ  jÕ  jr  jo  j‘
  jŽ
  jË
  jÈ
  jÑ  jÎ  j   j  j˜  j•  jì  jé  j   j  j  j  j  j  uŒ	nametypes”}”(j(  ‰jL  ‰jÖ  ‰jN  ‰j0  ‰jØ  ‰jr  ‰j‘
  ‰jË
  ‰jÑ  ‰j   ‰j˜  ‰jì  ‰j   ‰j  ‰j  ‰uh}”(j%  h£jI  j  jÓ  jO  jK  jÙ  j-  jQ  jÕ  j3  jo  jÛ  jŽ
  ju  jÈ
  j”
  jÎ  jÎ
  j  jÔ  j•  jf  jé  j£  j  jï  j  jU  j  j  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.