> Michael Ellerman <michael@ellerman.id.au> wrote on 02.11.2007 07:30:08:
quoted text
> 
> > On Wed, 2007-10-31 at 20:48 +0100, Christoph Raisch wrote:
> > > Michael Ellerman <michael@ellerman.id.au> wrote on 30.10.2007 23:50:36:
> > If that's really the way it works then eHEA is more or less broken for
> > kdump I'm afraid.
> 
> We think we have a way to workaround this, but let me first try to
> explain the base problem.
> 
> DD allocates HEA resources and gets firmware_handles for these resources.
> To free the resources DD needs to use exactly these handles.
> There's no generic firmware call "clean out all resources".
> Allocating the same resources twice does not work.

Can we get a new firmware call to do this?  

quoted text
> So a new kernel can't free the resources allocated by an old kernel,
> because the numeric values of the handles aren't known anymore.

How many possible handles are there?  

If the handles are lost, is the only way to clear out the HEA resources
is to reset the partition?

quoted text
> Potential Solution:
> Hea driver cleanup function hooks into ppc_md.machine_crash_shutdown
> and frees all firmware resources at shutdown time of the crashed kernel.

This means the crashed kernel now has to be trusted to shut down and
free up the resources.  Isn't trusting the crashing kernel in this way
against the whole kdump idea?

quoted text
> crash_kexec continues and loads new kernel.
> The new kernel restarts the HEA driver within kdump kernel, which will work
> because resources have been freed before.
> 
> Michael, would this work?
> 
> Gruss / Regards
> Christoph R.
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 
-
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/