From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Baoquan He <bhe@redhat.com>
Cc: linuxppc-dev@ozlabs.org, Akhil Raj <lf32.dev@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Dave Hansen <dave.hansen@linux.intel.com>,
Dave Young <dyoung@redhat.com>,
David Hildenbrand <david@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hari Bathini <hbathini@linux.ibm.com>,
Laurent Dufour <laurent.dufour@fr.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Mimi Zohar <zohar@linux.ibm.com>,
Naveen N Rao <naveen@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Schneider <vschneid@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
kexec@lists.infradead.org, x86@kernel.org
Subject: Re: [PATCH v17 0/6] powerpc/crash: Kernel handling of CPU and memory hotplug
Date: Fri, 1 Mar 2024 10:43:18 +0530 [thread overview]
Message-ID: <9dd60fea-5b6c-409d-bc55-8e27545b47d4@linux.ibm.com> (raw)
In-Reply-To: <ZeCL1EsQ/vLojCYs@MiWiFi-R3L-srv>
Hello Baoquan,
On 29/02/24 19:21, Baoquan He wrote:
> Hi Sourabh,
>
> On 02/26/24 at 02:11pm, Sourabh Jain wrote:
>> Commit 247262756121 ("crash: add generic infrastructure for crash
>> hotplug support") added a generic infrastructure that allows
>> architectures to selectively update the kdump image component during CPU
>> or memory add/remove events within the kernel itself.
>>
>> This patch series adds crash hotplug handler for PowerPC and enable
>> support to update the kdump image on CPU/Memory add/remove events.
>>
>> Among the 5 patches in this series, the first two patches make changes
>> to the generic crash hotplug handler to assist PowerPC in adding support
>> for this feature. The last three patches add support for this feature.
> The whole series looks good to me. I have acked patch 1 and 2. Leave
> those three ppc patches to ppc expert to review and approve. Thanks a
> lot for your great work.
Thanks for your feedback. I will soon send v18 to fix the two mirror
document issues
and will look forward to PPC maintainers to provide feedback on the rest
of the series.
Appreciate your support!
- Sourabh
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2024-03-01 5:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 8:41 [PATCH v17 0/6] powerpc/crash: Kernel handling of CPU and memory hotplug Sourabh Jain
2024-02-26 8:41 ` [PATCH v17 1/6] crash: forward memory_notify arg to arch crash hotplug handler Sourabh Jain
2024-02-26 8:41 ` [PATCH v17 2/6] crash: add a new kexec flag for hotplug support Sourabh Jain
2024-02-29 5:05 ` Sourabh Jain
2024-02-29 5:56 ` Baoquan He
2024-02-29 7:58 ` Sourabh Jain
2024-02-29 7:28 ` Baoquan He
2024-02-29 8:14 ` Sourabh Jain
2024-02-29 8:34 ` Sourabh Jain
2024-02-26 8:41 ` [PATCH v17 3/6] powerpc/kexec: move *_memory_ranges functions to ranges.c Sourabh Jain
2024-02-29 8:11 ` Baoquan He
2024-02-29 8:16 ` Sourabh Jain
2024-02-26 8:41 ` [PATCH v17 4/6] PowerPC/kexec: make the update_cpus_node() function public Sourabh Jain
2024-02-26 8:41 ` [PATCH v17 5/6] powerpc/crash: add crash CPU hotplug support Sourabh Jain
2024-02-26 8:41 ` [PATCH v17 6/6] powerpc/crash: add crash memory " Sourabh Jain
2024-02-29 13:51 ` [PATCH v17 0/6] powerpc/crash: Kernel handling of CPU and memory hotplug Baoquan He
2024-03-01 5:13 ` Sourabh Jain [this message]
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=9dd60fea-5b6c-409d-bc55-8e27545b47d4@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=bhe@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dyoung@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=laurent.dufour@fr.ibm.com \
--cc=lf32.dev@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=osalvador@suse.de \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
--cc=zohar@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