From: linas@austin.ibm.com (Linas Vepstas)
To: Luke Browning <lukebr@linux.vnet.ibm.com>
Cc: Michael Neuling <mikey@neuling.org>,
Jeff Garzik <jeff@garzik.org>,
Jan-Bernd Themann <themann@de.ibm.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thomas Klein <osstklei@de.ibm.com>,
linux-ppc <linuxppc-dev@ozlabs.org>,
Christoph Raisch <raisch@de.ibm.com>,
Paul Mackerras <paulus@samba.org>, Marcus Eder <meder@de.ibm.com>,
Stefan Roscher <stefan.roscher@de.ibm.com>
Subject: Re: [PATCH] ehea: Add kdump support
Date: Mon, 26 Nov 2007 12:11:49 -0600 [thread overview]
Message-ID: <20071126181148.GF4551@austin.ibm.com> (raw)
In-Reply-To: <1196091697.7513.30.camel@luke-laptop.br.ibm.com>
Hi,
On Mon, Nov 26, 2007 at 01:41:37PM -0200, Luke Browning wrote:
> On Mon, 2007-11-26 at 19:16 +1100, Michael Ellerman wrote:
>
> > For kdump we have to assume that the kernel is fundamentally broken,
If I may so humbly suggest: since ehea is a power6 thing only,
we should refocus our energies on "hypervisor assisted dump",
which solves all of these problems.
In short, upon crash, the hypervisor will reset the
pci devices into working order, and will then boot
a new fresh kernel into a tiny corner of ram. The rest
of ram is not cleared, and can be dumped. After the
dump, the mem is returned to general use.
The key point here, for ehea, is "the hypervisor
will reset he device state to something rational".
Preliminary patches are at
http://patchwork.ozlabs.org/linuxppc/patch?id=14884
and following.
--linas
next prev parent reply other threads:[~2007-11-26 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 13:33 [PATCH] ehea: Add kdump support Thomas Klein
2007-11-10 0:20 ` Michael Neuling
2007-11-26 8:16 ` Michael Ellerman
2007-11-26 10:45 ` Christoph Raisch
2007-11-27 0:35 ` Michael Neuling
2007-11-26 15:41 ` Luke Browning
2007-11-26 18:11 ` Linas Vepstas [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-13 15:18 [PATCH] ehea: add " Thomas Klein
2008-02-20 16:50 ` 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=20071126181148.GF4551@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=lukebr@linux.vnet.ibm.com \
--cc=meder@de.ibm.com \
--cc=mikey@neuling.org \
--cc=netdev@vger.kernel.org \
--cc=osstklei@de.ibm.com \
--cc=paulus@samba.org \
--cc=raisch@de.ibm.com \
--cc=stefan.roscher@de.ibm.com \
--cc=themann@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).