From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Eric DeVolder <eric.devolder@oracle.com>,
linuxppc-dev@ozlabs.org, mpe@ellerman.id.au
Cc: mahesh@linux.vnet.ibm.com, kexec@lists.infradead.org,
bhe@redhat.com, hbathini@linux.ibm.com
Subject: Re: [RFC v3 PATCH 0/5] In kernel handling of CPU hotplug events for crash kernel
Date: Fri, 25 Mar 2022 14:02:44 +0530 [thread overview]
Message-ID: <cebcb5d0-0468-57e9-c9b0-46de8766c724@linux.ibm.com> (raw)
In-Reply-To: <fbea3816-1a7b-3f9b-1ebf-1f388537af5b@oracle.com>
On 24/03/22 00:02, Eric DeVolder wrote:
>
>
> On 3/21/22 03:04, Sourabh Jain wrote:
>> This patch series implements the crash hotplug handler on PowerPC
>> introduced
>> by https://lkml.org/lkml/2022/3/3/674 patch series.
>>
>>
>> The Problem:
>> ============
>> Post hotplug/DLPAR events the capture kernel holds stale information
>> about the
>> system. Dump collection with stale capture kernel might end up in
>> dump capture
>> failure or an inaccurate dump collection.
>>
>>
>> Existing solution:
>> ==================
>> The existing solution to keep the capture kernel up-to-date is
>> observe the
>> hotplug event via udev rule and trigger a full capture kernel reload
>> post
>> hotplug event.
>>
>> Shortcomings:
>> ------------------------------------------------
>> - Leaves a window where kernel crash might not lead to successful dump
>> collection.
>> - Reloading all kexec components for each hotplug is inefficient.
>> Since only
>> one or two kexec components need to be updated due to hotplug
>> event reloading
>> all kexec component is redundant.
>> - udev rules are prone to races if hotplug events are frequent.
>>
>> More about issues with an existing solution is posted here:
>> - https://lkml.org/lkml/2020/12/14/532
>> -
>> https://lists.ozlabs.org/pipermail/linuxppc-dev/2022-February/240254.html
>>
>> Proposed Solution:
>> ==================
>> Instead of reloading all kexec segments on hotplug event, this patch
>> series
>> focuses on updating only the relevant kexec segment. Once the kexec
>> segments are loaded in the kernel reserved area then an arch-specific
>> hotplug handler
>> will update the relevant kexec segment based on hotplug event type.
>>
>> As mentioned above this patch series implemented a PowerPC crash hotplug
>> handler for the CPU. The crash hotplug handler memory is in our TODO
>> list.
>>
>>
>> A couple of minor changes are required to realize the benefit of the
>> patch
>> series:
>>
>> - disalble the udev rule:
>>
>> comment out the below line in kdump udev rule file:
> fwiw, this will need to be conditionalized on arch, ie to skip for
> ppc64. I'm doing the same for x86_64.
I think kexec-tools maintains a separate udev rule file for PowerPC. I
will ensure CPU rules gets removed from kdump udev rules once this
feature is upstream.
Thanks,
- Sourabh Jain
next prev parent reply other threads:[~2022-03-25 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 8:04 [RFC v3 PATCH 0/5] In kernel handling of CPU hotplug events for crash kernel Sourabh Jain
2022-03-21 8:04 ` [RFC v3 PATCH 1/5] powerpc/kexec: make update_cpus_node non-static Sourabh Jain
2022-03-21 8:04 ` [RFC v3 PATCH 2/5] powerpc/crash hp: introduce a new config option CRASH_HOTPLUG Sourabh Jain
2022-03-23 18:32 ` Eric DeVolder
2022-03-21 8:04 ` [RFC v3 PATCH 3/5] powrepc/crash hp: update kimage struct Sourabh Jain
2022-03-23 18:32 ` Eric DeVolder
2022-03-24 6:07 ` Sourabh Jain
2022-03-21 8:04 ` [RFC v3 PATCH 4/5] powerpc/crash hp: add crash hotplug support for kexec_file_load Sourabh Jain
2022-03-23 18:32 ` Eric DeVolder
2022-03-25 11:32 ` Sourabh Jain
2022-03-25 18:03 ` Laurent Dufour
2022-03-31 9:00 ` Sourabh Jain
2022-03-21 8:04 ` [RFC v3 PATCH 5/5] powerpc/crash hp: add crash hotplug support for kexec_load Sourabh Jain
2022-03-23 18:33 ` Eric DeVolder
2022-03-23 18:32 ` [RFC v3 PATCH 0/5] In kernel handling of CPU hotplug events for crash kernel Eric DeVolder
2022-03-25 8:32 ` Sourabh Jain [this message]
2022-03-25 17:04 ` Laurent Dufour
2022-03-31 9:05 ` Sourabh Jain
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=cebcb5d0-0468-57e9-c9b0-46de8766c724@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=eric.devolder@oracle.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
/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).