[patch 0/9] kdump: Patch series for s390 support

[Michael Holzheu]

Hello Vivec,

On Thu, 2011-07-14 at 13:55 -0400, Vivek Goyal wrote:

[snip]

> > The first thing we want to do is to check if
> > the purgatory is still fine, that is do a checksum. If we have the
> > infrastructure in place to do one checksum then we can easily do the
> > other checksums as well.
> 
> Some piece of code you have to assume is fine. Are you not already
> assuming that IPL code you have in first 64K bytes is fine and no
> body has overwritten it.

We can assume that the IPL dump code is fine, because it is freshly
loaded into memory. Only when the disk is somehow corrupted we have a
problem.

> Are you not assuming that hook in panic()
> (I think you are calling it shutdown trigger) is fine so that it
> can help you jump to right place.

Yes, that is correct for automatic dump in case of panic(). The panic()
path can fail.

But there are two other options where really *no* code that was in
memory, when the system crashed, is used for the dump process or
verification of kdump:
1) Manual IPL/boot of stand-alone dump by the operator via the virtual
guest console
2) Automatic IPL/boot of stand-alone dump by our z/VM hypervisor
watchdog

Michael