[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240808132423.0f313ffe@meshulam.tesarici.cz>
Date: Thu, 8 Aug 2024 13:24:23 +0200
From: Petr Tesařík <petr@...arici.cz>
To: Sourabh Jain <sourabhjain@...ux.ibm.com>
Cc: bhe@...hat.com, Hari Bathini <hbathini@...ux.ibm.com>,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, x86@...nel.org
Subject: Re: [PATCH] Document/kexec: Generalize crash hotplug description
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@...ux.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@...arici.cz>
> Cc: Hari Bathini <hbathini@...ux.ibm.com>
> Cc: kexec@...ts.infradead.org
> Cc: linux-kernel@...r.kernel.org
> Cc: linuxppc-dev@...ts.ozlabs.org
> Cc: x86@...nel.org
> Signed-off-by: Sourabh Jain <sourabhjain@...ux.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@...r.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.
> 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@...r.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
Powered by blists - more mailing lists