Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: kexec@lists.infradead.org
Subject: Re: [RFD] efi assisted kdump
Date: Tue, 27 Jan 2015 14:21:41 +0800	[thread overview]
Message-ID: <20150127062141.GC2506@darkstar.redhat.com> (raw)
In-Reply-To: <20150124170344.3b06a23e@hananiah.suse.cz>

Hi, Petr

On 01/24/15 at 05:03pm, Petr Tesarik wrote:
> On Sat, 24 Jan 2015 21:26:37 +0800
> Dave Young <dyoung@redhat.com> wrote:
> 
> > Hi,
> > 
> > Kdump has several limitations currently such as kdump kernel reboot will bypass
> > device shutdown path so device drivers should reset during initialization.
> > 
> >[...]
> > 
> > ppc64 has a feature "firmware assisted kdump", see below documentation:
> > Documentation/powerpc/firmware-assisted-dump.txt
> 
> Hi Dave,
> 
> while I'm no expert on either UEFI or IBM POWER, I'd like to warn you
> that fadump (firmware-assisted dump) on PPC is not quite optimal in its
> current form. One of the things that have always irritated me are
> excessive RAM requirements.
> 
> The problem is that there is only one reboot in fadump - after saving
> the dump, the secondary kernel discards the saved area and continues
> booting as usual. However, many kernel structuers must be already
> allocated at that point, e.g. the memmap array(s), but they are sized
> by the total RAM, not the limited amount available to the 2nd kernel.

Thanks for the comment.

I'm not sure I understand the RAM requirements you mentioned. I think you
are worrying about freeing oldmem to be used by 2nd kernel.

But we do not need to do same as power we can just reboot another time
as long as vmcore is saved. The main advantage is the capture kernel can
boot with all devices being reset. 

> 
> This issue is not so bad on a typical IBM POWER system, because these
> machines tend to be partitioned into many small LPARs, where each has
> relatively little RAM. But on a machine with 6TB RAM, you'll have to
> reserve approx. 84G merely for the memmap array on the secondary
> kernel's boot, which looks just a bit wasteful...
> 
> Maybe the two approaches can be combined somehow, so that the
> kdump system uses kexec() to transition into the production system, but
> that only works if a normal kexec does not have any of the issues
> you're trying to address.
> 
> Just my two cents,
> Petr Tesarik
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-01-27  6:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24 13:26 [RFD] efi assisted kdump Dave Young
2015-01-24 16:03 ` Petr Tesarik
2015-01-27  6:21   ` Dave Young [this message]
2015-01-27  9:14     ` Petr Tesarik
2015-01-26 14:08 ` Vivek Goyal
2015-01-27  6:24   ` Dave Young
2015-01-26 16:39 ` Matt Fleming
2015-01-27  6:37   ` Dave Young

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=20150127062141.GC2506@darkstar.redhat.com \
    --to=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=ptesarik@suse.cz \
    /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