[lkml]   [2011]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 0/9] kdump: Patch series for s390 support
On Thu, Jul 14, 2011 at 01:55:32PM -0400, Vivek Goyal wrote:

> > > So we first try to take purgatory path which does the checksum and is
> > > consistent with other architectures. If that does not work in case
> > > of hard hang, you always have the option of IPLing the stand alone tool
> > > later manually.
> >
> > How are we suddenly on the purgatory path again? The code that gets
> > control in case of a hard crash + IPL is the stand-alone dump tool,
> > not the purgatory code.
> I think that's the biggest contetion point. From the start of discussion
> you have this hardcoded requirement that the moment panic() happens
> you are jumping to some IPL code and that's what I am questioning. Why
> can't you execute some more code after panic() (purgatory), before
> you jump to IPL code (only if you have to).

In your parlance of shutdown actions, I think it is equivalnet to saying
that "kdump" is a shutdown action and that that means is that for specific
trigger points we will execute "crash_kexec()" function which will try
to capture the dump.

In user space I think one can modify the kexec-tools infrastrucuture a
bit so that one is able to define an entry point in case checksum of
loaded segment failes. Once you are loding kdump kernel, you can define
that entry point. (And this would be jump to IPL etc.).


 \ /
  Last update: 2011-07-14 20:07    [W:0.130 / U:32.128 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site