[PATCH 2/2] kdump shutdown hook support

2008-01-17 Thread Michael Neuling
This adds hooks into the default_machine_crash_shutdown so drivers can register a function to be run in the first kernel before we hand off to the second kernel. This should only be used in exceptional circumstances, like where the device can't be reset in the second kernel alone (as is the case w

[PATCH 2/2] kdump shutdown hook support

2008-01-16 Thread Michael Neuling
This adds hooks into the default_machine_crash_shutdown so drivers can register a function to be run in the first kernel before we hand off to the second kernel. This should only be used in exceptional circumstances, like where the device can't be reset in the second kernel alone (as is the case w

[PATCH 2/2] kdump shutdown hook support

2007-12-13 Thread Michael Neuling
This adds hooks into the default_machine_crash_shutdown so drivers can register a function to be run in the first kernel before we hand off to the second kernel. This should only be used in exceptional circumstances, like where the device can't be reset in the second kernel alone (as is the case w

Re: [PATCH 2/2] kdump shutdown hook support

2007-12-12 Thread Olof Johansson
On Wed, Dec 12, 2007 at 11:12:24PM -0600, Olof Johansson wrote: > Hi, > > + __delay(SETJMP_MACHINE_CHECK_DELAY); > > Where is this defined? Oops, nevermind. In 1/2, of course. :-) -Olof ___ Linuxppc-dev mailing list Linuxppc-dev@ozl

Re: [PATCH 2/2] kdump shutdown hook support

2007-12-12 Thread Olof Johansson
Hi, On Thu, Dec 13, 2007 at 02:16:18PM +1100, Michael Neuling wrote: > Index: clone3/arch/powerpc/kernel/crash.c > === > --- clone3.orig/arch/powerpc/kernel/crash.c > +++ clone3/arch/powerpc/kernel/crash.c > @@ -32,6 +32,8 @@ > #inc

[PATCH 2/2] kdump shutdown hook support

2007-12-12 Thread Michael Neuling
This adds hooks into the default_machine_crash_shutdown so drivers can register a function to be run in the first kernel before we hand off to the second kernel. This should only be used in exceptional circumstances, like where the device can't be reset in the second kernel alone (as is the case w

Re: [PATCH 2/2] kdump shutdown hook support

2007-12-12 Thread Michael Neuling
> > > + if (setjmp(crash_shutdown_buf) == 0) { > > + asm volatile("sync; isync"); > > + crash_shutdown_handles[i](); > > + asm volatile("sync; isync"); > > + __delay(200); > > This looks a bit random. Why the handc

Re: [PATCH 2/2] kdump shutdown hook support

2007-12-12 Thread Michael Neuling
In message <[EMAIL PROTECTED]> you wrote: > > --=-Kza0KCx0MG8nsjfq7kOz > Content-Type: text/plain > Content-Transfer-Encoding: quoted-printable > > On Wed, 2007-12-12 at 16:45 +1100, Michael Neuling wrote: > > This adds hooks into the default_machine_crash_shutdown so drivers can > > register a

Re: [PATCH 2/2] kdump shutdown hook support

2007-12-12 Thread Michael Ellerman
On Wed, 2007-12-12 at 16:45 +1100, Michael Neuling wrote: > This adds hooks into the default_machine_crash_shutdown so drivers can > register a function to be run in the first kernel before we hand off > to the second kernel. This should only be used in exceptional > circumstances, like where the

Re: [PATCH 2/2] kdump shutdown hook support

2007-12-11 Thread Olof Johansson
Hi, A couple of comments below. -Olof On Wed, Dec 12, 2007 at 04:45:12PM +1100, Michael Neuling wrote: > Index: linux-2.6-ozlabs/arch/powerpc/kernel/crash.c > === > --- linux-2.6-ozlabs.orig/arch/powerpc/kernel/crash.c > +++ linux-

[PATCH 2/2] kdump shutdown hook support

2007-12-11 Thread Michael Neuling
This adds hooks into the default_machine_crash_shutdown so drivers can register a function to be run in the first kernel before we hand off to the second kernel. This should only be used in exceptional circumstances, like where the device can't be reset in the second kernel alone (as is the case w