diff options
| author |   James Morse <james.morse@arm.com> | 2020-05-01 17:45:43 +0100 |
|---|---|---|
| committer |   Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2020-05-19 19:51:11 +0200 |
| commit | 8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462 (patch) | |
| tree | 88aa885e59229f4f1b59b7fa0972aa43b642ed6c /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | ACPI: APEI: Kick the memory_failure() queue for synchronous errors (diff) | |
| download | wireguard-linux-8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462.tar.xz wireguard-linux-8fcc4ae6faf8b455eeef00bc9ae70744e3b0f462.zip | |
arm64: acpi: Make apei_claim_sea() synchronise with APEI's irq work
APEI is unable to do all of its error handling work in nmi-context, so
it defers non-fatal work onto the irq_work queue. arch_irq_work_raise()
sends an IPI to the calling cpu, but this is not guaranteed to be taken
before returning to user-space.
Unless the exception interrupted a context with irqs-masked,
irq_work_run() can run immediately. Otherwise return -EINPROGRESS to
indicate ghes_notify_sea() found some work to do, but it hasn't
finished yet.
With this apei_claim_sea() returning '0' means this external-abort was
also notification of a firmware-first RAS error, and that APEI has
processed the CPER records.
Signed-off-by: James Morse <james.morse@arm.com>
Tested-by: Tyler Baicar <baicar@os.amperecomputing.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions