Thread (47 messages) 47 messages, 2 authors, 2019-08-19

Re: [PATCH v4 11/25] powernv/fadump: register kernel metadata address with opal

From: Hari Bathini <hbathini@linux.ibm.com>
Date: 2019-08-19 15:54:01


On 14/08/19 3:51 PM, Mahesh Jagannath Salgaonkar wrote:
On 8/14/19 12:36 PM, Hari Bathini wrote:
quoted

On 13/08/19 4:11 PM, Mahesh J Salgaonkar wrote:
quoted
On 2019-07-16 17:03:15 Tue, Hari Bathini wrote:
quoted
OPAL allows registering address with it in the first kernel and
retrieving it after MPIPL. Setup kernel metadata and register its
address with OPAL to use it for processing the crash dump.

Signed-off-by: Hari Bathini <hbathini@linux.ibm.com>
---
[...]
quoted
quoted
What if kernel crashes before metadata area is initialized ?
registered_regions would be '0'. So, it is treated as fadump is not registered case.
Let me
initialize metadata explicitly before registering the address with f/w to avoid any assumption...
Do you want to do that before memblock reservation ? Should we move this
to setup_fadump() ?
Better here as failing early would mean we could fall back to KDump..
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help