Lines Matching refs:Z
47 register files. However the `Z` register file effectively extends the length of
49 file will now access the lower 128 bits of the corresponding `Z` register.
52 (SVL), a power-of-two between 128 and 2048 inclusive. Each `Z` register is SVL
73 `V`/`Z` and `P` register files, and to set all `FPSR` flags. When software
154 `Z`, `P`, and `SVCR` values and then clears `PSTATE.SM`. xnu later restores
191 `PSTATE.SM`. Likewise `machine_restore_sme_context()` doesn't manipulate the `Z`
226 More critically, the `Z`, `P`, `ZA`, and `ZT0` register files are also shared
241 still forced to spill `Z` and `P` state to memory anytime the guest traps to EL2
264 | `ARM_SVE_Z_STATE1`, `ARM_SME_Z_STATE2` | `arm_sve_z_state_t` | Z register file |
276 `Z` can architecturally be up to 8 kilobytes in size. Since this is too large
277 to fit in a single Mach message, xnu's Mach thread-state APIs divide the `Z`
294 * Access `Z` or `P` state when the target thread's `SVCR.SM` bit is cleared
315 // Are Z and P valid?