From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: "Petr Tesařík" <petr@tesarici.cz>
Cc: bhe@redhat.com, Hari Bathini <hbathini@linux.ibm.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org
Subject: Re: [PATCH] Document/kexec: Generalize crash hotplug description
Date: Fri, 9 Aug 2024 11:05:28 +0530 [thread overview]
Message-ID: <ba0c218b-fb38-41a6-8339-265cc75466aa@linux.ibm.com> (raw)
In-Reply-To: <20240808132423.0f313ffe@meshulam.tesarici.cz>
Hello Petr,
On 08/08/24 16:54, Petr Tesařík wrote:
> Hi Sourabh,
>
> sorry for late reply, was on vacation and then catching up...
>
> On Mon, 5 Aug 2024 10:38:29 +0530
> Sourabh Jain <sourabhjain@linux.ibm.com> wrote:
>
>> Commit 79365026f869 ("crash: add a new kexec flag for hotplug support")
>> generalizes the crash hotplug support to allow architectures to update
>> multiple kexec segments on CPU/Memory hotplug and not just elfcorehdr.
>> Therefore, update the relevant kernel documentation to reflect the same.
>>
>> No functional change.
>>
>> Cc: Petr Tesarik <petr@tesarici.cz>
>> Cc: Hari Bathini <hbathini@linux.ibm.com>
>> Cc: kexec@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linuxppc-dev@lists.ozlabs.org
>> Cc: x86@kernel.org
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> ---
>>
>> Discussion about the documentation update:
>> https://lore.kernel.org/all/68d0328d-531a-4a2b-ab26-c97fd8a12e8b@linux.ibm.com/
>>
>> ---
>> .../ABI/testing/sysfs-devices-memory | 6 ++--
>> .../ABI/testing/sysfs-devices-system-cpu | 6 ++--
>> .../admin-guide/mm/memory-hotplug.rst | 5 ++--
>> Documentation/core-api/cpu_hotplug.rst | 10 ++++---
>> kernel/crash_core.c | 29 ++++++++++++-------
>> 5 files changed, 33 insertions(+), 23 deletions(-)
>>
>> diff --git a/Documentation/ABI/testing/sysfs-devices-memory b/Documentation/ABI/testing/sysfs-devices-memory
>> index a95e0f17c35a..421acc8e2c6b 100644
>> --- a/Documentation/ABI/testing/sysfs-devices-memory
>> +++ b/Documentation/ABI/testing/sysfs-devices-memory
>> @@ -115,6 +115,6 @@ What: /sys/devices/system/memory/crash_hotplug
>> Date: Aug 2023
>> Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
>> Description:
>> - (RO) indicates whether or not the kernel directly supports
>> - modifying the crash elfcorehdr for memory hot un/plug and/or
>> - on/offline changes.
>> + (RO) indicates whether or not the kernel update of kexec
>> + segments on memory hot un/plug and/or on/offline events,
>> + avoiding the need to reload kdump kernel.
> This sentence somehow lacks a verb. My suggestion:
>
> (RO) indicates whether or not the kernel updates relevant kexec
> segments on memory hot un/plug and/or on/offline events, avoiding the
> need to reload kdump kernel.
Thanks for the review. I will update the document as suggested.
- Sourabh Jain
>
>> diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
>> index 325873385b71..f4ada1cd2f96 100644
>> --- a/Documentation/ABI/testing/sysfs-devices-system-cpu
>> +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
>> @@ -703,9 +703,9 @@ What: /sys/devices/system/cpu/crash_hotplug
>> Date: Aug 2023
>> Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
>> Description:
>> - (RO) indicates whether or not the kernel directly supports
>> - modifying the crash elfcorehdr for CPU hot un/plug and/or
>> - on/offline changes.
>> + (RO) indicates whether or not the kernel update of kexec
>> + segments on CPU hot un/plug and/or on/offline events,
>> + avoiding the need to reload kdump kernel.
> Same as above.
>
> Otherwise LGTM.
>
> Petr T
next prev parent reply other threads:[~2024-08-09 5:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 5:08 Sourabh Jain
2024-08-08 11:24 ` Petr Tesařík
2024-08-09 5:35 ` Sourabh Jain [this message]
2024-08-09 1:48 ` Baoquan He
2024-08-09 11:03 ` 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=ba0c218b-fb38-41a6-8339-265cc75466aa@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=petr@tesarici.cz \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®