[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1193784636.32504.4.camel@concordia>
Date: Wed, 31 Oct 2007 09:50:36 +1100
From: Michael Ellerman <michael@...erman.id.au>
To: Christoph Raisch <RAISCH@...ibm.com>
Cc: Jan-Bernd Themann <THEMANN@...ibm.com>,
Jeff Garzik <jeff@...zik.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-ppc <linuxppc-dev@...abs.org>,
Marcus Eder <MEDER@...ibm.com>,
netdev <netdev@...r.kernel.org>, ossthema@...ux.vnet.ibm.com,
Stefan Roscher <stefan.roscher@...ibm.com>,
Thomas Q Klein <TKLEIN@...ibm.com>
Subject: Re: [PATCH] ehea: add kexec support
On Tue, 2007-10-30 at 09:39 +0100, Christoph Raisch wrote:
>
> Michael Ellerman <michael@...erman.id.au> wrote on 28.10.2007 23:32:17:
> >
> >
> > How do you plan to support kdump?
> >
>
> When kexec is fully supported kdump should work out of the box
> as for any other ethernet card (if you load the right eth driver).
> There's nothing specific to kdump you have to handle in
> ethernet device drivers.
> Hope I didn't miss anything here...
Perhaps. When we kdump the kernel does not call the reboot notifiers, so
the code Jan-Bernd just added won't get called. So the eHEA resources
won't be freed. When the kdump kernel tries to load the eHEA driver what
will happen?
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)
Powered by blists - more mailing lists