From: Michael Ellerman <michael@ellerman.id.au>
To: Christoph Raisch <RAISCH@de.ibm.com>
Cc: Thomas Q Klein <TKLEIN@de.ibm.com>,
ossthema@linux.vnet.ibm.com, Jeff Garzik <jeff@garzik.org>,
Jan-Bernd Themann <THEMANN@de.ibm.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ppc <linuxppc-dev@ozlabs.org>,
Marcus Eder <MEDER@de.ibm.com>,
Stefan Roscher <stefan.roscher@de.ibm.com>
Subject: Re: [PATCH] ehea: add kexec support
Date: Wed, 31 Oct 2007 09:50:36 +1100 [thread overview]
Message-ID: <1193784636.32504.4.camel@concordia> (raw)
In-Reply-To: <OF79E7ACE7.5D0488CE-ONC1257384.002E58C0-C1257384.002F8561@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Tue, 2007-10-30 at 09:39 +0100, Christoph Raisch wrote:
>
> Michael Ellerman <michael@ellerman.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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
To: Christoph Raisch <RAISCH@de.ibm.com>
Cc: Jan-Bernd Themann <THEMANN@de.ibm.com>,
Jeff Garzik <jeff@garzik.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-ppc <linuxppc-dev@ozlabs.org>,
Marcus Eder <MEDER@de.ibm.com>, netdev <netdev@vger.kernel.org>,
ossthema@linux.vnet.ibm.com,
Stefan Roscher <stefan.roscher@de.ibm.com>,
Thomas Q Klein <TKLEIN@de.ibm.com>
Subject: Re: [PATCH] ehea: add kexec support
Date: Wed, 31 Oct 2007 09:50:36 +1100 [thread overview]
Message-ID: <1193784636.32504.4.camel@concordia> (raw)
In-Reply-To: <OF79E7ACE7.5D0488CE-ONC1257384.002E58C0-C1257384.002F8561@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
On Tue, 2007-10-30 at 09:39 +0100, Christoph Raisch wrote:
>
> Michael Ellerman <michael@ellerman.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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-30 22:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 12:37 [PATCH] ehea: add kexec support Jan-Bernd Themann
2007-10-26 12:37 ` Jan-Bernd Themann
2007-10-28 22:32 ` Michael Ellerman
2007-10-28 22:32 ` Michael Ellerman
2007-10-30 8:39 ` Christoph Raisch
2007-10-30 8:39 ` Christoph Raisch
2007-10-30 22:50 ` Michael Ellerman [this message]
2007-10-30 22:50 ` Michael Ellerman
2007-10-31 19:48 ` Christoph Raisch
2007-10-31 19:48 ` Christoph Raisch
2007-11-02 6:30 ` Michael Ellerman
2007-11-02 6:30 ` Michael Ellerman
2007-11-02 10:19 ` Christoph Raisch
2007-11-02 10:19 ` Christoph Raisch
2007-11-03 6:06 ` Michael Neuling
2007-11-03 6:06 ` Michael Neuling
2007-11-05 14:24 ` Christoph Raisch
2007-11-05 14:24 ` Christoph Raisch
2007-10-29 9:47 ` Jeff Garzik
2007-10-29 9:47 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1193784636.32504.4.camel@concordia \
--to=michael@ellerman.id.au \
--cc=MEDER@de.ibm.com \
--cc=RAISCH@de.ibm.com \
--cc=THEMANN@de.ibm.com \
--cc=TKLEIN@de.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=ossthema@linux.vnet.ibm.com \
--cc=stefan.roscher@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.