summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorMoshe Shemesh <moshe@nvidia.com>2026-07-02 14:17:25 +0300
committerPaolo Abeni <pabeni@redhat.com>2026-07-08 11:23:49 +0200
commitf6ec46b7e2b227499200fb071752ea653f145f3d (patch)
tree1f475238b9cd5b06bb774993c153f3d1f4e96104 /tools/perf/scripts/python/event_analyzing_sample.py
parenta6cfd2762eb18cde4eb34906599ffa7b07c2ed60 (diff)
devlink: print controller prefix for non-zero controller
The controller prefix (c<N>) in phys_port_name is currently restricted to external host controllers. This layout sufficed when DPUs only had a single local controller and one or more external host controllers. However, newer devices can have multiple controllers within the DPU itself, even within a single host environment. To support these topologies, allow drivers to report the controller number regardless of the "external" flag status. Any non-zero controller number will now be explicitly reported, even for single-host or local DPU controllers. Existing ports with controller=0 are unaffected. Update documentation and kdoc to clarify that a non-zero controller number does not require the external flag to be set. Signed-off-by: Moshe Shemesh <moshe@nvidia.com> Reviewed-by: Parav Pandit <parav@nvidia.com> Signed-off-by: Tariq Toukan <tariqt@nvidia.com> Link: https://patch.msgid.link/20260702111726.816985-2-tariqt@nvidia.com Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions