Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>, kexec@lists.infradead.org
Cc: Aditya Gupta <adityag@linux.ibm.com>, Baoquan He <bhe@redhat.com>,
	Coiby Xu <coxu@redhat.com>,
	Mahesh Salgaonkar <mahesh@linux.ibm.com>
Subject: Re: [PATCH 3/3] doc/hotplug: update man and --help
Date: Mon, 10 Jun 2024 17:54:59 +0530	[thread overview]
Message-ID: <ab5c7865-720f-4c17-baff-527fc1c4d9d4@linux.ibm.com> (raw)
In-Reply-To: <8ba124ad-13a4-43e3-8838-a29e2b7fd8e7@linux.ibm.com>

Hello Hari,

On 10/06/24 14:49, Hari Bathini wrote:
>
>
> On 22/05/24 6:43 pm, Sourabh Jain wrote:
>> Update the man page and --help option to make the description of the
>> --hotplug option easier to understand.
>>
>> Cc: Aditya Gupta <adityag@linux.ibm.com>
>> Cc: Baoquan He <bhe@redhat.com>
>> Cc: Coiby Xu <coxu@redhat.com>
>> Cc: Hari Bathini <hbathini@linux.ibm.com>
>> Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> ---
>>   kexec/kexec.8 | 8 ++++----
>>   kexec/kexec.c | 3 ++-
>>   2 files changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/kexec/kexec.8 b/kexec/kexec.8
>> index 9e995fe..7dddae9 100644
>> --- a/kexec/kexec.8
>> +++ b/kexec/kexec.8
>> @@ -140,10 +140,10 @@ Open a help file for
>>   .BR kexec .
>>   .TP
>>   .B \-\-hotplug
>
> Can we have the description changed like:
>
>> -Setup for kernel modification of the elfcorehdr. This option performs
>> -the steps needed to support kernel updates to the elfcorehdr in the
>> -presence of hot un/plug and/or on/offline events. This option only
>> -useful for KEXEC_LOAD syscall.
>> +Helps avoid kdump kernel reload on CPU/Memory hotplug or on/offline 
>> events.
>> +If this option is enabled, the kexec segments will be set up in a 
>> way that
>> +the kernel can safely update them on CPU/memory hotplug and/or 
>> on/offline
>> +events. This option is only useful for the KEXEC_LOAD syscall.
>
> "Setup kexec segments such that kernel can safely update them on 
> CPU/Memory hot add/remove events. If this option is enabled, kernel does
> in-kernel update of kexec segments on CPU/Memory hot add/remove events.
> Helps avoid the need to reload kdump kernel."
>
>
>>   .TP
>>   .B \-i\ (\-\-no-checks)
>>   Fast reboot, no memory integrity checks.
>> diff --git a/kexec/kexec.c b/kexec/kexec.c
>> index 034cea6..2b06438 100644
>> --- a/kexec/kexec.c
>> +++ b/kexec/kexec.c
>> @@ -1093,7 +1093,8 @@ void usage(void)
>>              "                      back to the compatibility syscall 
>> when file based\n"
>>              "                      syscall is not supported or the 
>> kernel did not\n"
>>              "                      understand the image (default)\n"
>> -           " --hotplug            Setup for kernel modification of 
>> elfcorehdr.\n"
>
>> +           " --hotplug            Helps avoid kdump kernel reload on 
>> CPU/Memory hotplug\n"
>> +           "              or on/offline events.\n"
>
> "Do in-kernel update of kexec segments on CPU/Memory hot add/remove 
> events. This avoids the need to reload kdump kernel."

The suggested descriptions look good to me. I will update them in the 
next version.

Thanks,
Sourabh Jain


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2024-06-10 12:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 13:13 [PATCH 1/3] kexec_load: Use new kexec flag for hotplug support Sourabh Jain
2024-05-22 13:13 ` [PATCH 2/3] powerpc/kexec_load: add " Sourabh Jain
2024-06-10  9:38   ` Hari Bathini
2024-06-10 12:19     ` Sourabh Jain
2024-05-22 13:13 ` [PATCH 3/3] doc/hotplug: update man and --help Sourabh Jain
2024-06-10  9:19   ` Hari Bathini
2024-06-10 12:24     ` Sourabh Jain [this message]
2024-05-28 11:33 ` [PATCH 1/3] kexec_load: Use new kexec flag for hotplug support Aditya Gupta
2024-05-29 13:13   ` Sourabh Jain
2024-05-30  6:23     ` Aditya Gupta
2024-06-10  8:52 ` Hari Bathini
2024-06-10 11:42   ` 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=ab5c7865-720f-4c17-baff-527fc1c4d9d4@linux.ibm.com \
    --to=sourabhjain@linux.ibm.com \
    --cc=adityag@linux.ibm.com \
    --cc=bhe@redhat.com \
    --cc=coxu@redhat.com \
    --cc=hbathini@linux.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=mahesh@linux.ibm.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