diff options
| author | Greg Kurz <[email protected]> | 2019-09-11 17:52:18 +0200 |
|---|---|---|
| committer | Michael Ellerman <[email protected]> | 2019-09-12 09:27:05 +1000 |
| commit | 6ccb4ac2bf8a35c694ead92f8ac5530a16e8f2c8 (patch) | |
| tree | e2680d33f9b4590f7e3ecf70c7af8310a333d433 /tools/perf/scripts/python | |
| parent | 92c94dfb69e350471473fd3075c74bc68150879e (diff) | |
powerpc/xive: Fix bogus error code returned by OPAL
There's a bug in skiboot that causes the OPAL_XIVE_ALLOCATE_IRQ call
to return the 32-bit value 0xffffffff when OPAL has run out of IRQs.
Unfortunatelty, OPAL return values are signed 64-bit entities and
errors are supposed to be negative. If that happens, the linux code
confusingly treats 0xffffffff as a valid IRQ number and panics at some
point.
A fix was recently merged in skiboot:
e97391ae2bb5 ("xive: fix return value of opal_xive_allocate_irq()")
but we need a workaround anyway to support older skiboots already
in the field.
Internally convert 0xffffffff to OPAL_RESOURCE which is the usual error
returned upon resource exhaustion.
Cc: [email protected] # v4.12+
Signed-off-by: Greg Kurz <[email protected]>
Reviewed-by: Cédric Le Goater <[email protected]>
Signed-off-by: Michael Ellerman <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions