From: Pratyush Anand <panand@redhat.com>
To: Dave Young <dyoung@redhat.com>, Pingfan Liu <piliu@redhat.com>
Cc: Xunlei Pang <xpang@redhat.com>,
kexec@lists.infradead.org, Baoquan He <bhe@redhat.com>,
kernelfans@gmail.com
Subject: Re: [PATCHv2 2/2] [fs] proc/vmcore: check the dummy place holder for offline cpu to avoid warning
Date: Tue, 20 Dec 2016 21:08:29 +0530 [thread overview]
Message-ID: <6691e874-e47a-0028-a2f8-59e431613d6f@redhat.com> (raw)
In-Reply-To: <20161219024018.GB29921@dhcp-128-65.nay.redhat.com>
On Monday 19 December 2016 08:10 AM, Dave Young wrote:
> Hi, Pingfan
>
> On 12/19/16 at 10:08am, Pingfan Liu wrote:
>> > kexec-tools always allocates program headers for present cpus. But
>> > when crashing, offline cpus have dummy headers. We do not copy these
>> > dummy notes into ELF file, also have no need of warning on them.
> I still think it is not worth such a fix, if you feel a lot of warnings
> in case large cpu numbers, I think you can change the pr_warn to
> pr_warn_once, we do not care the null cpu notes if it has nothing bad
> to the vmcore.
>
I agree. Warning is more like information here. May be, we can count the
number of times real_sz was 0, and then can print an info at the end in
stead of warning, like..."N number of CPUs would have been offline,
PT_NOTE entries was absent for them."
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-12-20 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 2:08 [PATCHv2 1/2] kexec: add a dummy note for each offline cpu Pingfan Liu
2016-12-19 2:08 ` [PATCHv2 2/2] [fs] proc/vmcore: check the dummy place holder for offline cpu to avoid warning Pingfan Liu
2016-12-19 2:40 ` Dave Young
2016-12-20 15:38 ` Pratyush Anand [this message]
2016-12-21 3:26 ` Xunlei Pang
2016-12-21 3:57 ` Pratyush Anand
2016-12-21 4:52 ` Xunlei Pang
2016-12-21 7:15 ` Liu ping fan
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=6691e874-e47a-0028-a2f8-59e431613d6f@redhat.com \
--to=panand@redhat.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kernelfans@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=piliu@redhat.com \
--cc=xpang@redhat.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