diff options
| author | Daniel Thompson <[email protected]> | 2016-08-19 17:13:09 +0100 |
|---|---|---|
| committer | Marc Zyngier <[email protected]> | 2016-09-12 19:46:19 +0100 |
| commit | 91ef84428a86b75a52e15c6fe4f56b446ba75f93 (patch) | |
| tree | 46066d44e3ddccef1b4d0056955eb59ffc67cf54 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 04c8b0f82c7d5a9a1c296eef914ae3bb820bcb85 (diff) | |
irqchip/gic-v3: Reset BPR during initialization
Currently, when running on FVP, CPU 0 boots up with its BPR changed from
the reset value. This renders it impossible to (preemptively) prioritize
interrupts on CPU 0.
This is harmless on normal systems since Linux typically does not
support preemptive interrupts. It does however cause problems in
systems with additional changes (such as patches for NMI simulation).
Many thanks to Andrew Thoelke for suggesting the BPR as having the
potential to harm preemption.
Suggested-by: Andrew Thoelke <[email protected]>
Signed-off-by: Daniel Thompson <[email protected]>
Signed-off-by: Marc Zyngier <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions