[patch v3 0/8] kdump: Patch series for s390 support (version 3)
From: Michael Holzheu
Date: Fri Aug 12 2011 - 09:49:27 EST
I updated the patch series according to our last discussions. As you requested,
I removed the "#if !defined(CONFIG_S390)" in the panic function.
The semantics is now as follows:
If kdump is loaded, kdump is always triggered for panic and PSW restart
(s390 NMI). If kdump is not loaded, the s390 shutdown actions defined
under /sys/firmware are executed as we are doing it already today.
I also added again patches for stand-alone dump integration:
For s390 we add a parameter to the purgatory entry point. When "0" is passed,
purgatory only returns the result of the checksum test. When "1" is passed,
purgatory triggers kdump. So we call purgatory twice. First for checking and
second time for execution. You can argue that it would be better to call
purgatory only once and it returns only, if checksums are invalid.
Unfortunately this would be very hard to implement for us, because we
switch to the boot CPU before kdump is finally triggered and after that
currently it is not possible to return from the called function.
| call_s390_shutdown_actions() -> stand-alone dump
PSW restart --+
crash_kexec +--> kdump loaded? --> machine_kexec()
+--> kdump not loaded --> return
machine_kexec +-> purgatory(0)==0 -> switch to IPL cpu -> purgatory(1) -> kdump
+-> purgatory(0)!=0 -> return
See patches  and  for details.
Does that sound ok for you?
[1-3] common code changes (could you please ACC patches  and ?)
 s390 kdump preparation patch
 s390 kdump backend
 s390 stand-alone dump/shutdown actions integration
 kexec-tools: s390 kdump backend for kexec-tools
 kexec-tools: s390 stand-alone dump/shutdown actions integration
Main changes compared to version 1:
1. We use purgatory code
2. We use pre-allocated ELF core header
3. Registers are saved in old kernel
4. Removed meminfo
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/