o, 0));
}
}
+}
+EXPORT_SYMBOL_GPL(pci_traverse_sibling_nodes_and_scan_slot);
What is the need for exporting the above function?
+
DECLARE_PCI_FIXUP_EARLY(PCI_ANY_ID, PCI_ANY_ID, pci_dev_pdn_setup);
- Sourabh Jain
Gupta
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: "Naveen N. Rao"
Signed-off-by: Sourabh Jain
---
* No changes in v2.
---
arch/powerpc/kexec/core_64.c | 53 +---
1 file changed, 37 insertions(+), 16 deletions(-)
diff --git a
parameter to the setup_new_fdt_ppc64 function, it was
noticed that there were a couple of unused parameters, so they were
removed.
Cc: Aditya Gupta
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: "Naveen N. Rao"
Signed-off-by: Sourabh Jain
---
Changelog:
lerman
Cc: "Naveen N. Rao"
Sourabh Jain (2):
powerpc/kexec_file: fix extra size calculation for kexec FDT
powerpc/kexec_file: fix cpus node update to FDT
arch/powerpc/include/asm/kexec.h | 6 ++--
arch/powerpc/kexec/core_64.c | 53 +--
arch/powerpc/kexec
Gupta
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: "Naveen N. Rao"
Signed-off-by: Sourabh Jain
---
arch/powerpc/kexec/core_64.c | 53 +---
1 file changed, 37 insertions(+), 16 deletions(-)
diff --git a/arch/powerpc/kexec
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: "Naveen N. Rao"
Sourabh Jain (2):
powerpc/kexec_file: fix extra size calculation for kexec FDT
powerpc/kexec_file: fix cpus node update to FDT
arch/powerpc/include/asm/kexec.h | 6 ++--
arch/powerpc/kexec
parameter to the setup_new_fdt_ppc64 function, it was
noticed that there were a couple of unused parameters, so they were
removed.
Cc: Aditya Gupta
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: "Naveen N. Rao"
Signed-off-by: Sourabh Jain
---
arch/powerpc/include/a
Rothwell
Signed-off-by: Sourabh Jain
---
arch/powerpc/kexec/crash.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/powerpc/kexec/crash.c b/arch/powerpc/kexec/crash.c
index 21b193e938a3..9ac3266e4965 100644
--- a/arch/powerpc/kexec/crash.c
+++ b/arch/powerpc/kexec
odate additional memory ranges and the
elfcorehdr segment is not considered for SHA calculation, making it safe
to update.
The changes related to this feature are kept under the CRASH_HOTPLUG
config, and it is enabled by default.
Signed-off-by: Sourabh Jain
Acked-by: Hari Bathini
Cc: Akhil Raj
C
nabled by default.
Signed-off-by: Sourabh Jain
Acked-by: Hari Bathini
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Greg Kroah-Hartman
Cc: Laurent
red to be public. Mark them as
static and removed them from kexec_ranges.h header file.
Finally, remove the CONFIG_KEXEC_FILE build dependency for range.c
because it is required for other config, such as CONFIG_CRASH_DUMP.
No functional changes are intended.
Signed-off-by: Sourabh Jain
Acked-by: H
lls.
No functional changes are intended.
Signed-off-by: Sourabh Jain
Acked-by: Hari Bathini
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: G
ng the x86 crash hotplug support in line with the above points,
the following changes have been made:
- Introduce the arch_crash_hotplug_support function to process kexec
flags and determine crash hotplug support
- Remove the arch_crash_hotplug_[cpu|memory]_support functions
Signed-off-by: So
Zohar
Cc: Naveen N Rao
Cc: Oscar Salvador
Cc: Stephen Rothwell
Cc: Thomas Gleixner
Cc: Valentin Schneider
Cc: Vivek Goyal
Cc: ke...@lists.infradead.org
Cc: x...@kernel.org
Sourabh Jain (6):
crash: forward memory_notify arg to arch crash hotplug handler
crash: add a new kexec flag for hotplug
()` and
`arch_crash_handle_hotplug_event()` to accept the `memory_notify` object
as an argument from crash memory hotplug notifier.
Since no such object is available in the case of CPU hotplug event, the
crash CPU hotplug notifier `crash_cpuhp_online()` passes NULL to the
crash hotplug handler.
Signed-off-by: Sourabh Jain
Acked
gic number in the future. Therefore, remove the
corresponding TODO from the document.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
---
.../arch/powerpc/firmware-assisted-dump.
ump kernel. This eliminates the need to regenerate the elfcorehdr
during memory hotplug or online/offline events.
Create a sysfs entry at /sys/kernel/fadump/hotplug_ready to let
userspace know that fadump re-registration is not required for memory
add/remove events.
Signed-off-by: Sourabh Jain
: if either first/crashed kernel or second/fadump kernel do not have
the changes introduced here then kernel fail to collect the dump and
prints relevant error message on the console.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: "Aneesh Kumar K.V"
Cc: Hari Bathini
Cc: Mahesh Salg
ndentation issues reported by the checkpatch script.
- Rebased it to 6.6.0-rc3
v1: 17 Sep 2023
https://lore.kernel.org/all/20230917080225.561627-1-sourabhj...@linux.ibm.com/
Cc: Aditya Gupta
Cc: "Aneesh Kumar K.V"
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
com/
Cc: Aditya Gupta
Cc: "Aneesh Kumar K.V"
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
Sourabh Jain (3):
powerpc: make fadump resilient with memory add/remove events
powerpc/fadump: add hotplug_ready sysfs interface
Documentation/powerpc:
gic number in the future. Therefore, remove the
corresponding TODO from the document.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
---
.../arch/powerpc/firmware-assisted-dump.
: if either first/crashed kernel or second/fadump kernel do not have
the changes introduced here then kernel fail to collect the dump and
prints relevant error message on the console.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: "Aneesh Kumar K.V"
Cc: Hari Bathini
Cc: Mahesh Salg
ump kernel. This eliminates the need to regenerate the elfcorehdr
during memory hotplug or online/offline events.
Create a sysfs entry at /sys/kernel/fadump/hotplug_ready to let
userspace know that fadump re-registration is not required for memory
add/remove events.
Signed-off-by: Sourabh Jain
odate additional memory ranges and the
elfcorehdr segment is not considered for SHA calculation, making it safe
to update.
The changes related to this feature are kept under the CRASH_HOTPLUG
config, and it is enabled by default.
Signed-off-by: Sourabh Jain
Acked-by: Hari Bathini
Cc: Akhil Raj
C
nabled by default.
Signed-off-by: Sourabh Jain
Acked-by: Hari Bathini
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Greg Kroah-Hartman
Cc: Laurent
red to be public. Mark them as
static and removed them from kexec_ranges.h header file.
Finally, remove the CONFIG_KEXEC_FILE build dependency for range.c
because it is required for other config, such as CONFIG_CRASH_DUMP.
No functional changes are intended.
Signed-off-by: Sourabh Jain
Acked-by: H
lls.
No functional changes are intended.
Signed-off-by: Sourabh Jain
Acked-by: Hari Bathini
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: G
ng the x86 crash hotplug support in line with the above points,
the following changes have been made:
- Introduce the arch_crash_hotplug_support function to process kexec
flags and determine crash hotplug support
- Remove the arch_crash_hotplug_[cpu|memory]_support functions
Signed-off-by: So
thini
Cc: Laurent Dufour
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Mimi Zohar
Cc: Naveen N Rao
Cc: Oscar Salvador
Cc: Thomas Gleixner
Cc: Valentin Schneider
Cc: Vivek Goyal
Cc: ke...@lists.infradead.org
Cc: x...@kernel.org
Sourabh Jain (6):
crash: forward memory_notify arg to arch cra
()` and
`arch_crash_handle_hotplug_event()` to accept the `memory_notify` object
as an argument from crash memory hotplug notifier.
Since no such object is available in the case of CPU hotplug event, the
crash CPU hotplug notifier `crash_cpuhp_online()` passes NULL to the
crash hotplug handler.
Signed-off-by: Sourabh Jain
Acked
Hello Hari,
On 11/03/24 14:08, Hari Bathini wrote:
On 17/02/24 12:50 pm, Sourabh Jain wrote:
Due to changes in memory resources caused by either memory hotplug or
online/offline events, the elfcorehdr, which describes the CPUs and
memory of the crashed kernel to the kernel that collects
On 02/03/24 18:49, Hari Bathini wrote:
On 26/02/24 2:11 pm, Sourabh Jain wrote:
Extend the arch crash hotplug handler, as introduced by the patch title
("powerpc: add crash CPU hotplug support"), to also support memory
add/remove events.
Elfcorehdr describes the memory of the cr
Hello Hari,
On 02/03/24 18:47, Hari Bathini wrote:
On 26/02/24 2:11 pm, Sourabh Jain wrote:
Commit a72bbec70da2 ("crash: hotplug support for kexec_load()")
introduced a new kexec flag, `KEXEC_UPDATE_ELFCOREHDR`. Kexec tool uses
this flag to indicate to the kernel that it is safe
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 k
Hello
On 29/02/24 12:58, Baoquan He wrote:
On 02/26/24 at 02:11pm, Sourabh Jain wrote:
..snip...
diff --git a/kernel/crash_core.c b/kernel/crash_core.c
index 70fa8111a9d6..630c4fd7ea39 100644
--- a/kernel/crash_core.c
+++ b/kernel/crash_core.c
@@ -496,7 +496,7 @@ static DEFINE_MUTEX
On 29/02/24 13:41, Baoquan He wrote:
On 02/26/24 at 02:11pm, Sourabh Jain wrote:
Move the following functions form kexec/{file_load_64.c => ranges.c} and
make them public so that components other KEXEC_FILE can also
Hello Baoquan,
On 29/02/24 12:58, Baoquan He wrote:
On 02/26/24 at 02:11pm, Sourabh Jain wrote:
..snip...
diff --git a/kernel/crash_core.c b/kernel/crash_core.c
index 70fa8111a9d6..630c4fd7ea39 100644
--- a/kernel/crash_core.c
+++ b/kernel/crash_core.c
@@ -496,7 +496,7 @@ static
On 29/02/24 11:26, Baoquan He wrote:
On 02/29/24 at 10:35am, Sourabh Jain wrote:
Hello Baoquan,
Do you have any comments or suggestions for this patch series, especially
for this patch?
Have applied this series and reviewing, will ack or add comment if any
concern. Thanks.
Thanks
Hello Michael and Aneesh,
Please let me know if you have any comments or suggestions for this
patch series.
Thanks,
Sourabh
On 17/02/24 12:50, Sourabh Jain wrote:
Due to changes in memory resources caused by either memory hotplug or
online/offline events, the elfcorehdr, which describes
Hello Baoquan,
Do you have any comments or suggestions for this patch series,
especially for this patch?
Thanks,
Sourabh
On 26/02/24 14:11, Sourabh Jain wrote:
Commit a72bbec70da2 ("crash: hotplug support for kexec_load()")
introduced a new kexec flag, `KEXEC_UPDATE_ELFCOREHDR`.
odate additional memory ranges and the
elfcorehdr segment is not considered for SHA calculation, making it safe
to update.
The changes related to this feature are kept under the CRASH_HOTPLUG
config, and it is enabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc:
nabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Greg Kroah-Hartman
Cc: Hari Bathini
Cc: Laurent Duf
lls.
No functional changes are intended.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Greg Kroah-Hartman
Cc: H
red to be public. Mark them as
static and removed them from kexec_ranges.h header file.
Finally, remove the CONFIG_KEXEC_FILE build dependency for range.c
because it is required for other config, such as CONFIG_CRASH_DUMP.
No functional changes are intended.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
_file_load system calls. This
simplifies kernel checks to identify hotplug support for the currently
loaded kdump image by just examining the value of @hotplug_support.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
MD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Greg Kroah-Hartman
Cc: Hari Bathini
Cc: Laurent Dufour
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Mimi Zohar
Cc: Naveen N Rao
Cc: Oscar Salvador
Cc: Thomas Gleixner
Cc: Valentin Schn
()` and
`arch_crash_handle_hotplug_event()` to accept the `memory_notify` object
as an argument from crash memory hotplug notifier.
Since no such object is available in the case of CPU hotplug event, the
crash CPU hotplug notifier `crash_cpuhp_online()` passes NULL to the
crash hotplug handler.
Signed-off-by: Sourabh Jain
Acked
Hello Hari,
Build failure detected.
On 13/02/24 17:01, Hari Bathini wrote:
Remove CONFIG_CRASH_DUMP dependency on CONFIG_KEXEC. CONFIG_KEXEC_CORE
was used at places where CONFIG_CRASH_DUMP or CONFIG_CRASH_RESERVE was
appropriate. Replace with appropriate #ifdefs to support CONFIG_KEXEC
and
On 22/02/24 09:28, Baoquan He wrote:
On 02/22/24 at 09:01am, Sourabh Jain wrote:
Hello Baoquan,
There are a lot of code movements introduced by your patch series, 'Split
crash out from kexec and clean up related config items.'
https://lore.kernel.org/all
of the above patch series?
Thanks,
Sourabh Jain
On 17/02/24 13:44, Sourabh Jain wrote:
Commit a72bbec70da2 ("crash: hotplug support for kexec_load()")
introduced a new kexec flag, `KEXEC_UPDATE_ELFCOREHDR`. Kexec tool uses
this flag to indicate to the kernel that it is safe to modify the
Hello Baoquan,
On 19/01/24 20:22, Baoquan He wrote:
Now move the relevant codes into separate files:
kernel/crash_reserve.c, include/linux/crash_reserve.h.
And add config item CRASH_RESERVE to control its enabling.
Feels like this patch is more about vmcore_info.[c|h] and CONFIG_VMCORE_INFO
Hello Baoquan,
Thank you for reorganizing the kexec and kdump code with a well-defined
configuration structure.
While reviewing the patch series, I noticed a few typos.
On 19/01/24 20:22, Baoquan He wrote:
Both kdump and fa_dump of ppc rely on crashkernel reservation. Move the
relevant codes
Hello Hari,
On 23/01/24 15:39, Hari Bathini wrote:
On 11/01/24 7:39 pm, Sourabh Jain wrote:
Due to changes in memory resources caused by either memory hotplug or
online/offline events, the elfcorehdr, which describes the CPUs and
memory of the crashed kernel to the kernel that collects
odate additional memory ranges and the
elfcorehdr segment is not considered for SHA calculation, making it safe
to update.
The changes related to this feature are kept under the CRASH_HOTPLUG
config, and it is enabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc:
nabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Greg Kroah-Hartman
Cc: Hari Bathini
Cc: Laurent Duf
, these functions are utilized for in-kernel updates
to kdump image during CPU/Memory hotplug or online/offline events for
both kexec_load and kexec_file_load syscalls.
There is no intended functional change.
Signed-off-by: Sourabh Jain
Reviewed-by: Laurent Dufour
Cc: Akhil Raj
Cc: Andrew Morton
Cc
_file_load system calls. This
simplifies kernel checks to identify hotplug support for the currently
loaded kdump image by just examining the value of @hotplug_support.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
()` and
`arch_crash_handle_hotplug_event()` to accept the `memory_notify` object
as an argument from crash memory hotplug notifier.
Since no such object is available in the case of CPU hotplug event, the
crash CPU hotplug notifier `crash_cpuhp_online()` passes NULL to the
crash hotplug handler.
Signed-off-by: Sourabh Jain
Acked
ichael Ellerman
Cc: Mimi Zohar
Cc: Naveen N Rao
Cc: Oscar Salvador
Cc: Thomas Gleixner
Cc: Valentin Schneider
Cc: Vivek Goyal
Cc: ke...@lists.infradead.org
Cc: x...@kernel.org
Sourabh Jain (5):
crash: forward memory_notify arg to arch crash hotplug handler
crash: add a new kexec flag fo
gic number in the future. Therefore, remove the
corresponding TODO from the document.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
---
.../arch/powerpc/firmware-assisted-dump.
ump kernel. This eliminates the need to regenerate the elfcorehdr
during memory hotplug or online/offline events.
Create a sysfs entry at /sys/kernel/fadump/hotplug_ready to let
userspace know that fadump re-registration is not required for memory
add/remove events.
Signed-off-by: Sourabh Jain
and fadump
kernels.
Note: if either first/crashed kernel or second/fadump kernel do not have
the changes introduced here then kernel fail to collect the dump and
prints relevant error message on the console.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc
ll/20230917080225.561627-1-sourabhj...@linux.ibm.com/
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
Sourabh Jain (3):
powerpc: make fadump resilient with memory add/remove events
powerpc/fadump: add hotplug_ready sysfs
On 13/02/24 08:51, Baoquan He wrote:
On 02/12/24 at 07:27pm, Sourabh Jain wrote:
Hello Baoquan,
On 05/02/24 08:40, Baoquan He wrote:
Hi Sourabh,
..
diff --git a/include/linux/kexec.h b/include/linux/kexec.h
index 802052d9c64b..7880d74dc5c4 100644
--- a/include/linux/kexec.h
+++ b
Hello Baoquan,
On 05/02/24 08:40, Baoquan He wrote:
Hi Sourabh,
Thanks for the great work. There are some concerns, please see inline
comments.
Thank you :)
On 01/11/24 at 04:21pm, Sourabh Jain wrote:
..
Now, if the kexec tool sends KEXEC_CRASH_HOTPLUG_SUPPORT kexec flag
On 05/02/24 08:41, Baoquan He wrote:
On 01/11/24 at 04:21pm, Sourabh Jain wrote:
In the event of memory hotplug or online/offline events, the crash
memory hotplug notifier `crash_memhp_notifier()` receives a
`memory_notify` object but doesn't forward that object to the
generic
On 23/01/24 15:52, Hari Bathini wrote:
On 11/01/24 4:21 pm, Sourabh Jain wrote:
Extend the arch crash hotplug handler, as introduced by the patch title
("powerpc: add crash CPU hotplug support"), to also support memory
add/remove events.
Elfcorehdr describes the memory of the cr
gic number in the future. Therefore, remove the
corresponding TODO from the document.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
---
.../arch/powerpc/firmware-assisted-dump.
ump kernel. This eliminates the need to regenerate the elfcorehdr
during memory hotplug or online/offline events.
Create a sysfs entry at /sys/kernel/fadump/hotplug_ready to let
userspace know that fadump re-registration is not required for memory
add/remove events.
Signed-off-by: Sourabh Jain
of pt_regs
and cpu_mask are not the same across the crashed and fadump kernel.
Note: if either first/crashed kernel or second/fadump kernel do not have
the changes introduced here then kernel fail to collect the dump and
prints relevant error message on the console.
Signed-off-by: Sourabh Jain
Cc
ll/20230917080225.561627-1-sourabhj...@linux.ibm.com/
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
Sourabh Jain (3):
powerpc: make fadump resilient with memory add/remove events
powerpc/fadump: add hotplug_ready sysfs interfa
()` and
`arch_crash_handle_hotplug_event()` to accept the `memory_notify` object
as an argument from crash memory hotplug notifier.
Since no such object is available in the case of CPU hotplug event, the
crash CPU hotplug notifier `crash_cpuhp_online()` passes NULL to the
crash hotplug handler.
Signed-off-by: Sourabh Jain
Cc: Akhil
Thomas Gleixner
Cc: Valentin Schneider
Cc: Vivek Goyal
Cc: ke...@lists.infradead.org
Cc: x...@kernel.org
Sourabh Jain (5):
crash: forward memory_notify arg to arch crash hotplug handler
crash: add a new kexec flag for hotplug support
powerpc/kexec: turn some static helper functions public
odate additional memory ranges and the
elfcorehdr segment is not considered for SHA calculation, making it safe
to update.
The changes related to this feature are kept under the CRASH_HOTPLUG
config, and it is enabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc:
, these functions are utilized for in-kernel updates
to kdump image during CPU/Memory hotplug or online/offline events for
both kexec_load and kexec_file_load syscalls.
There is no intended functional change.
Signed-off-by: Sourabh Jain
Reviewed-by: Laurent Dufour
Cc: Akhil Raj
Cc: Andrew Morton
Cc
nabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Greg Kroah-Hartman
Cc: Hari Bathini
Cc: Laurent Duf
_file_load system calls. This
simplifies kernel checks to identify hotplug support for the currently
loaded kdump image by just examining the value of @hotplug_support.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Hello Baoquan,
While replying to this email earlier, I mistakenly pressed "Reply to List"
instead of "Reply to All." Consequently, my response was sent only to
powerpc
mailing list.
On 17/12/23 06:29, Baoquan He wrote:
On 12/17/23 at 12:27am, Sourabh Jain wrote:
On 16/
Hello Aditya,
On 17/12/23 14:11, Aditya Gupta wrote:
Hi sourabh,
On 06/12/23 01:48, Hari Bathini wrote:
From: Sourabh Jain
Currently, fadump on pseries assumes a single boot memory region even
though f/w supports more than one boot memory region. Add support for
more boot memory regions
On 17/12/23 06:29, Baoquan He wrote:
On 12/17/23 at 12:27am, Sourabh Jain wrote:
On 16/12/23 15:11, Baoquan He wrote:
On 12/15/23 at 12:17pm, Sourabh Jain wrote:
..
diff --git a/include/linux/kexec.h b/include/linux/kexec.h
index 0f6ea35879ee..bcedb7625b1f 100644
--- a/include/linux
On 16/12/23 15:11, Baoquan He wrote:
On 12/15/23 at 12:17pm, Sourabh Jain wrote:
..
diff --git a/include/linux/kexec.h b/include/linux/kexec.h
index 0f6ea35879ee..bcedb7625b1f 100644
--- a/include/linux/kexec.h
+++ b/include/linux/kexec.h
@@ -319,6 +319,7 @@ struct kimage {
#ifdef
Hello Hari,
On 06/12/23 01:48, Hari Bathini wrote:
For fadump case, passing additional parameters to dump capture kernel
helps in minimizing the memory footprint for it and also provides the
flexibility to disable components/modules, like hugepages, that are
hindering the boot process of the
Hello Hari,
On 06/12/23 01:48, Hari Bathini wrote:
From: Sourabh Jain
Currently, fadump on pseries assumes a single boot memory region even
though f/w supports more than one boot memory region. Add support for
more boot memory regions to make the implementation flexible for any
enhancements
Hello Baoquan,
On 15/12/23 07:58, Baoquan He wrote:
On 12/11/23 at 02:00pm, Sourabh Jain wrote:
The commit a72bbec70da2 ("crash: hotplug support for kexec_load()")
introduced a new kexec flag, `KEXEC_UPDATE_ELFCOREHDR`. Kexec tool uses
this flag to indicate kernel that it is safe
On 15/12/23 06:53, Baoquan He wrote:
On 12/11/23 at 02:00pm, Sourabh Jain wrote:
..
diff --git a/arch/powerpc/include/asm/kexec_ranges.h
b/arch/powerpc/include/asm/kexec_ranges.h
index f83866a19e87..802abf580cf0 100644
--- a/arch/powerpc/include/asm/kexec_ranges.h
+++ b/arch/powerpc
Hello Baoquan,
On 14/12/23 19:43, Baoquan He wrote:
On 12/11/23 at 02:00pm, Sourabh Jain wrote:
Architectures' specific functions `arch_crash_hotplug_cpu_support()` and
`arch_crash_hotplug_memory_support()` advertise the kernel's capability
to update the kdump image on CPU and Memory hotplug
nabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Eric DeVolder
Cc: Greg Kroah-Hartman
Cc: Hari B
s related to this feature are kept under the CRASH_HOTPLUG
config, and it is enabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Eric DeVolder
Cc: Greg Kroah-Hartman
Cc: Hari Bathini
Cc: Laurent Dufour
Dufour
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Mimi Zohar
Cc: Naveen N Rao
Cc: Oscar Salvador
Cc: Thomas Gleixner
Cc: Valentin Schneider
Cc: Vivek Goyal
Cc: ke...@lists.infradead.org
Cc: x...@kernel.org
Sourabh Jain (6):
crash: forward memory_notify arg to arch crash hotplug
, these functions are utilized for in-kernel updates
to kdump image during CPU/Memory hotplug or online/offline events for
both kexec_load and kexec_file_load syscalls.
There is no intended functional change.
Signed-off-by: Sourabh Jain
Reviewed-by: Laurent Dufour
Cc: Akhil Raj
Cc: Andrew Morton
Cc
()` and
`arch_crash_handle_hotplug_event()` to accept the `memory_notify` object
as an argument from crash memory hotplug notifier.
Since no such object is available in the case of CPU hotplug event, the
crash CPU hotplug notifier `crash_cpuhp_online()` passes NULL to the
crash hotplug handler.
Signed-off-by: Sourabh Jain
Cc: Akhil
.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Aneesh Kumar K.V
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Eric DeVolder
Cc: Greg Kroah-Hartman
Cc: Hari Bathini
Cc: Laurent
gic number in the future. Therefore, remove the
corresponding TODO from the document.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
Cc: Aneesh Kumar K.V
Cc: Hari Bathini
Cc: Mahesh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
---
.../arch/powerpc/firmware-assisted-dump.
ump kernel. This eliminates the need to regenerate the elfcorehdr
during memory hotplug or online/offline events.
Create a sysfs entry at /sys/kernel/fadump/hotplug_ready to let
userspace know that fadump re-registration is not required for memory
add/remove events.
Signed-off-by: Sourabh Jain
of pt_regs
and cpu_mask are not the same across the crashed and fadump kernel.
Note: if either first/crashed kernel or second/fadump kernel do not have
the changes introduced here kernel fail to collect the dump and prints
relevant error message on console.
Signed-off-by: Sourabh Jain
Cc: Aditya Gupta
sh Salgaonkar
Cc: Michael Ellerman
Cc: Naveen N Rao
Sourabh Jain (3):
powerpc: make fadump resilient with memory add/remove events
powerpc/fadump: add hotplug_ready sysfs interface
Documentation/powerpc: update fadump implementation details
Documentation/ABI/testing/sysfs-kernel-fadump
nabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: Eric DeVolder
Cc: Greg Kroah-Hartman
Cc: Hari Bathini
Cc: Laurent Duf
s related to this feature are kept under the CRASH_HOTPLUG
config, and it is enabled by default.
Signed-off-by: Sourabh Jain
Cc: Akhil Raj
Cc: Andrew Morton
Cc: Baoquan He
Cc: Borislav Petkov (AMD)
Cc: Boris Ostrovsky
Cc: Christophe Leroy
Cc: Dave Hansen
Cc: Dave Young
Cc: David Hildenbrand
Cc: E
, these functions are utilized for in-kernel updates
to kdump image during CPU/Memory hotplug or online/offline events for
both kexec_load and kexec_file_load syscalls.
There is no intended functional change.
Signed-off-by: Sourabh Jain
Reviewed-by: Laurent Dufour
Cc: Akhil Raj
Cc: Andrew Morton
Cc
1 - 100 of 355 matches
Mail list logo
