diff options
| author | Sean V Kelley <[email protected]> | 2020-11-24 10:55:30 -0600 |
|---|---|---|
| committer | Bjorn Helgaas <[email protected]> | 2020-12-04 11:18:58 -0600 |
| commit | aa344bc8b727b47b4350b59d8166216a3f351e55 (patch) | |
| tree | 63f5eb611461fb68a684cc24bd925625e5eed309 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 05e9ae19ab83881a0f33025bd1288e41e552a34b (diff) | |
PCI/ERR: Clear AER status only when we control AER
In some cases a bridge may not exist as the hardware controlling may be
handled only by firmware and so is not visible to the OS. This scenario is
also possible in future use cases involving non-native use of RCECs by
firmware. In this scenario, we expect the platform to retain control of the
bridge and to clear error status itself.
Clear error status only when the OS has native control of AER.
Signed-off-by: Sean V Kelley <[email protected]>
Signed-off-by: Bjorn Helgaas <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions