diff options
| author | Lukas Wunner <[email protected]> | 2019-03-20 11:05:30 +0000 |
|---|---|---|
| committer | Bjorn Helgaas <[email protected]> | 2019-03-25 22:59:07 +0000 |
| commit | 0fa635aec9abd718bd18c0bda2261351a0811efc (patch) | |
| tree | 28feed152619c3557db954549f513abcb9bdc797 /tools/perf/scripts/python/check-perf-trace.py | |
| parent | PCI/LINK: Clear bandwidth notification interrupt before enabling it (diff) | |
| download | kernel-0fa635aec9abd718bd18c0bda2261351a0811efc.tar.gz kernel-0fa635aec9abd718bd18c0bda2261351a0811efc.zip | |
PCI/LINK: Deduplicate bandwidth reports for multi-function devices
If a multi-function device's bandwidth is already limited when it is
enumerated, a message is logged only for function 0. By contrast, when
downtraining occurs after enumeration, a message is logged for all
functions. That's because the former uses pcie_report_downtraining(),
whereas the latter uses __pcie_print_link_status() (which doesn't filter
functions != 0). I am seeing this happen on a MacBookPro9,1 with a GPU
(function 0) and an integrated HDA controller (function 1).
Avoid this incongruence by calling pcie_report_downtraining() in both
cases.
Signed-off-by: Lukas Wunner <[email protected]>
Signed-off-by: Bjorn Helgaas <[email protected]>
Reviewed-by: Alexandru Gagniuc <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions