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>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCH v2 3/3] doc/hotplug: update man and --help
Date: Wed, 26 Jun 2024 16:38:37 +0530 [thread overview]
Message-ID: <6f4cf5a2-70d1-437c-bb41-3a9a4a27df87@linux.ibm.com> (raw)
In-Reply-To: <7c06b691-d961-42af-9779-a2a98456c8e3@linux.ibm.com>
On 26/06/24 15:51, Hari Bathini wrote:
>
>
> On 14/06/24 12:37 am, 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>
>> Cc: Simon Horman <horms@kernel.org>
>
> Minor nits below...
>
> Otherwise, looks good.
>
> Acked-by: Hari Bathini <hbathini@linux.ibm.com>
I will include the changes suggested below in v3.
Thanks for the Ack.
- Sourabh Jain
>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> ---
>>
>> Changelog:
>>
>> Since v1:
>> - Updated --hotplug option description
>>
>> ---
>> kexec/kexec.8 | 8 ++++----
>> kexec/kexec.c | 4 +++-
>> 2 files changed, 7 insertions(+), 5 deletions(-)
>>
>> diff --git a/kexec/kexec.8 b/kexec/kexec.8
>> index 9e995fe..92fa3d5 100644
>> --- a/kexec/kexec.8
>> +++ b/kexec/kexec.8
>> @@ -140,10 +140,10 @@ Open a help file for
>> .BR kexec .
>> .TP
>> .B \-\-hotplug
>> -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.
>> +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.
>
> s/events. Helps avoid the need/events, thus avoiding the need/
>
>> .TP
>> .B \-i\ (\-\-no-checks)
>> Fast reboot, no memory integrity checks.
>> diff --git a/kexec/kexec.c b/kexec/kexec.c
>> index 034cea6..db8e2b3 100644
>> --- a/kexec/kexec.c
>> +++ b/kexec/kexec.c
>> @@ -1093,7 +1093,9 @@ 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 Do in-kernel update of kexec
>> segments on CPU/Memory\n"
>
>> + " hot add/remove events. This avoids
>> the need to reload\n"
>
> s/events. This avoids/events, avoiding/
>
>> + " kdump kernel or on/offline events.\n"
>
> s/kernel or on/kernel on online/
>
>> " -d, --debug Enable debugging to help spot a
>> failure.\n"
>> " -S, --status Return 1 if the type (by default
>> crash) is loaded,\n"
>> " 0 if not.\n"
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2024-06-26 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 19:07 [PATCH v2 1/3] kexec_load: Use new kexec flag for hotplug support Sourabh Jain
2024-06-13 19:07 ` [PATCH v2 2/3] powerpc/kexec_load: add " Sourabh Jain
2024-06-26 10:07 ` Hari Bathini
2024-06-26 11:07 ` Sourabh Jain
2024-06-13 19:07 ` [PATCH v2 3/3] doc/hotplug: update man and --help Sourabh Jain
2024-06-26 10:21 ` Hari Bathini
2024-06-26 11:08 ` Sourabh Jain [this message]
2024-06-25 8:21 ` [PATCH v2 1/3] kexec_load: Use new kexec flag for hotplug support Sourabh Jain
2024-06-26 3:50 ` Baoquan He
2024-06-26 4:07 ` Sourabh Jain
2024-06-26 5:19 ` Sourabh Jain
2024-06-26 6:54 ` Baoquan He
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=6f4cf5a2-70d1-437c-bb41-3a9a4a27df87@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=horms@kernel.org \
--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