diff options
| author | Ben Horgan <ben.horgan@arm.com> | 2026-05-15 09:58:25 +0100 |
|---|---|---|
| committer | Will Deacon <will@kernel.org> | 2026-07-16 14:44:12 +0100 |
| commit | 9469764292e0d6825c9bf51d75682e3a623b9b6b (patch) | |
| tree | 75dc25240e7d60f8df868a177eb4cfa74bf05a1e /tools/perf/scripts/python/stackcollapse.py | |
| parent | e057b94772328221405b067c3a85fe479b915dc8 (diff) | |
arm_mpam: Fix software reset values of MPAMCFG_PRI
Priority partitioning is not supported other than to set the per-PARTID
defaults in MPAMCFG_PRI, INTPRI and DSPRI, to the highest priority. When 0
is the lowest priority, all ones is the highest priority. However, these
values are calculated with an extra higher bit set.
Luckily, there is still no chance of setting functional bits incorrectly.
When the priority widths are maximal, this is ensured as the fields have
width 16 and a u16 holds the value for each field. When the widths are
smaller, the higher order bits beyond the advertised widths,
MPAMF_PRI_IDR.DSPRI_WD and MPAMF_PRI_IDR.INTPRI_WD, in the priority fields
INTPRI and DSPRI are not used to calculate the priority. It is not
specified whether these higher order bits are RAZ/WI or Res0 and so it is
desirable not to set them to avoid the chance of misleading reads.
Correct the priority reset values.
Fixes: 880df85d8673 ("arm_mpam: Probe and reset the rest of the features")
Signed-off-by: Ben Horgan <ben.horgan@arm.com>
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
