From: Xunlei Pang <xpang@redhat.com>
To: Liu ping fan <kernelfans@gmail.com>, xlpang@redhat.com
Cc: kexec@lists.infradead.org, Dave Young <dyoung@redhat.com>,
Pingfan Liu <piliu@redhat.com>, Baoquan He <bhe@redhat.com>
Subject: Re: [PATCH 1/2] kexec: add a dummy note for each offline cpu
Date: Wed, 14 Dec 2016 17:10:31 +0800 [thread overview]
Message-ID: <58510C87.7020209@redhat.com> (raw)
In-Reply-To: <CAFgQCTvFC92nXFYzpUs6fwbzeemDs1otDSW7j+iqyJ=3e-OACw@mail.gmail.com>
On 12/14/2016 at 04:56 PM, Liu ping fan wrote:
> On Wed, Dec 14, 2016 at 4:48 PM, Xunlei Pang <xpang@redhat.com> wrote:
>> On 12/14/2016 at 02:11 PM, Pingfan Liu wrote:
>>> kexec-tools always allocates program headers for each possible cpu. This
>>> incurs zero PT_NOTE for offline cpu. We mark this case so that later,
>>> the capture kernel can distinguish it from the mistake of allocated
>>> program header.
>>> The counterpart of the capture kernel comes in next patch.
>> Hmm, we can initialize the cpu crash note buf in crash_notes_memory_init(), needless
>> to do it at the crash moment, right?
>>
> The cpus can be on-off-on.., We can not know the user's action.
I meant we can add the fake note into the cpu note buf, then the crash happens, the online ones
will be overwritten with the real note data, while others(!online) will still be the fake note.
>
>> BTW, does this cause any issue, for example the crash utility can't parse the vmcore
>> properly? or just reproduce lots of warnings after offline multiple cpus?
>>
> No. This patch just place a mark on these offline cpu. The next patch
> for capture kernel will recognize this case, and ignore this kind of
> pt_note by the code:
> real_sz = 0; // although the size of this kind of PT_NOTE is not zero,
> but it contains nothing useful, so just ignore it
> phdr_ptr->p_memsz = real_sz
If there is any other vmcore functional issue besides throwing "Warning: Zero PT_NOTE entries found"?
Regards,
Xunlei
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-12-14 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 6:11 [PATCH 1/2] kexec: add a dummy note for each offline cpu Pingfan Liu
2016-12-14 6:11 ` [PATCH 2/2] [fs] proc/vmcore: check the dummy place holder for offline cpu to avoid warning Pingfan Liu
2016-12-14 23:56 ` Xunlei Pang
2016-12-15 3:04 ` Liu ping fan
2016-12-14 6:19 ` [PATCH 1/2] kexec: add a dummy note for each offline cpu Liu ping fan
2016-12-14 7:40 ` Baoquan He
2016-12-14 8:15 ` Liu ping fan
2016-12-14 8:25 ` Baoquan He
2016-12-14 8:39 ` Liu ping fan
2016-12-14 8:44 ` Baoquan He
2016-12-14 9:06 ` Liu ping fan
2016-12-14 8:48 ` Xunlei Pang
2016-12-14 8:56 ` Liu ping fan
2016-12-14 9:10 ` Xunlei Pang [this message]
2016-12-14 9:13 ` Liu ping fan
2016-12-14 23:49 ` Xunlei Pang
2016-12-15 7:16 ` Dave Young
2016-12-15 8:43 ` 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=58510C87.7020209@redhat.com \
--to=xpang@redhat.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=kernelfans@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=piliu@redhat.com \
--cc=xlpang@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 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.