summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/stackcollapse-report
diff options
context:
space:
mode:
authorDave Martin <dave.martin@arm.com>2026-09-11 17:36:13 +0100
committerBorislav Petkov (AMD) <bp@alien8.de>2026-09-14 08:20:25 -0700
commit942135446059a63778f1121a75c5b3c959341b47 (patch)
treea85b5a9a49ae3614d572bf2026bc083c85a48635 /tools/perf/scripts/python/bin/stackcollapse-report
parent255f92316ac1017478e9ace42cafdeb6c98c1f25 (diff)
fs/resctrl: Factor MBA parse-time conversion to be per-arch
The control value parser for the MB resource currently coerces the memory bandwidth percentage value from userspace to be an exact multiple of the rdt_resource::resctrl_membw::bw_gran parameter. On MPAM systems, this results in somewhat worse-than-worst-case rounding, since the bandwidth granularity advertised to resctrl by the MPAM driver is in general only an approximation to the actual hardware granularity on these systems, and the hardware bandwidth allocation control value is not natively a percentage -- necessitating a further conversion in the resctrl_arch_update_domains() path, regardless of the conversion done at parse time. For MPAM and x86 use their custom pre-prepared parse-time conversion, resctrl_arch_preconvert_bw(). This will avoid accumulated error from rounding the value twice on MPAM systems. For x86 systems there is no functional change. Clarify the documentation, but avoid overly exact promises. Clamping to bw_min and bw_max still feels generic: leave it in the core code, for now. Signed-off-by: Dave Martin <Dave.Martin@arm.com> Signed-off-by: Ben Horgan <Ben.Horgan@arm.com> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Reviewed-by: Ben Horgan <ben.horgan@arm.com> Reviewed-by: Reinette Chatre <reinette.chatre@intel.com> Reviewed-by: Gavin Shan <gshan@redhat.com> Link: https://patch.msgid.link/20260911163613.1131447-4-ben.horgan@arm.com
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions