From: "Michal Suchánek" <msuchanek@suse.de>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: Yangtao Li <tiny.windzz@gmail.com>,
Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Hari Bathini <hbathini@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/fadump: when fadump is supported register the fadump sysfs files.
Date: Wed, 4 Sep 2019 20:35:51 +0200 [thread overview]
Message-ID: <20190904203551.5b06abb6@naga> (raw)
In-Reply-To: <15be95b0-4cb2-1cf1-2fc1-ec313b9aa6f0@linux.ibm.com>
On Thu, 29 Aug 2019 10:58:16 +0530
Hari Bathini <hbathini@linux.ibm.com> wrote:
> On 28/08/19 10:57 PM, Michal Suchanek wrote:
> > Currently it is not possible to distinguish the case when fadump is
> > supported by firmware and disabled in kernel and completely unsupported
> > using the kernel sysfs interface. User can investigate the devicetree
> > but it is more reasonable to provide sysfs files in case we get some
> > fadumpv2 in the future.
> >
> > With this patch sysfs files are available whenever fadump is supported
> > by firmware.
> >
> > Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> > ---
>
> [...]
>
> > - if (!fw_dump.fadump_supported) {
> > + if (!fw_dump.fadump_supported && fw_dump.fadump_enabled) {
> > printk(KERN_ERR "Firmware-assisted dump is not supported on"
> > " this hardware\n");
> > - return 0;
> > }
>
> The above hunk is redundant with similar message already logged during
> early boot in fadump_reserve_mem() function. I am not strongly against
> this though. So...
I see this:
[ 0.000000] debug: ignoring loglevel setting.
[ 0.000000] Firmware-assisted dump is not supported on this hardware
[ 0.000000] Reserving 256MB of memory at 128MB for crashkernel (System RAM: 8192MB)
[ 0.000000] Allocated 5832704 bytes for 2048 pacas at c000000007a80000
[ 0.000000] Page sizes from device-tree:
[ 0.000000] base_shift=12: shift=12, sllp=0x0000, avpnm=0x00000000, tlbiel=1, penc=0
[ 0.000000] base_shift=16: shift=16, sllp=0x0110, avpnm=0x00000000, tlbiel=1, penc=1
[ 0.000000] Page orders: linear mapping = 16, virtual = 16, io = 16, vmemmap = 16
[ 0.000000] Using 1TB segments
[ 0.000000] Initializing hash mmu with SLB
Clearly the second message is logged from the above code. The duplicate
is capitalized: "Firmware-Assisted Dump is not supported on this
hardware" and I don't see it logged. So if anything is duplicate that
should be removed it is the message in fadump_reserve_mem(). It is not
clear why that one is not seen, though.
Thanks
Michal
prev parent reply other threads:[~2019-09-04 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:12 [PATCH rebased] powerpc/fadump: when fadump is supported register the fadump sysfs files Michal Suchanek
2019-08-27 12:27 ` Hari Bathini
2019-08-28 17:07 ` Michal Suchánek
2019-08-29 5:20 ` Hari Bathini
2019-08-28 17:27 ` [PATCH v2] " Michal Suchanek
2019-08-29 5:28 ` Hari Bathini
2019-09-04 18:35 ` Michal Suchánek [this message]
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=20190904203551.5b06abb6@naga \
--to=msuchanek@suse.de \
--cc=hbathini@linux.ibm.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=tiny.windzz@gmail.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).