From: Chen Zhou <chenzhou10@huawei.com> To: John Donnelly <john.p.donnelly@oracle.com> Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <catalin.marinas@arm.com>, <will@kernel.org>, <james.morse@arm.com>, <dyoung@redhat.com>, <bhsharma@redhat.com>, <horms@verge.net.au>, <kexec@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <guohanjun@huawei.com> Subject: Re: ` Date: Fri, 20 Dec 2019 09:44:52 +0800 [thread overview] Message-ID: <f8f5f7ae-718f-a411-26ff-999b0620dbce@huawei.com> (raw) In-Reply-To: <EA397BBF-56F6-4E8A-964D-ACB78F1DD9B4@oracle.com> Hi John, On 2019/12/20 2:33, John Donnelly wrote: > > >> On Dec 18, 2019, at 8:56 PM, Chen Zhou <chenzhou10@huawei.com> wrote: >> >> Hi John, >> >> On 2019/12/19 1:18, John Donnelly wrote: >>> HI >>> >>> SEE INLINE ON A QUESTION : >>> >>>> On Dec 17, 2019, at 8:07 PM, Chen Zhou <chenzhou10@huawei.com> wrote: >>>> >>>> Hi all, >>>> >>>> Friendly ping... >>>> >>>> On 2019/8/30 15:11, Chen Zhou wrote: >>>>> I am busy with other things, so it was a long time before this version was >>>>> released. >>>>> >>>>> This patch series enable reserving crashkernel above 4G in arm64. >>>>> >>>>> There are following issues in arm64 kdump: >>>>> 1. We use crashkernel=X to reserve crashkernel below 4G, which will fail >>>>> when there is no enough low memory. >>>>> 2. Currently, crashkernel=Y@X can be used to reserve crashkernel above 4G, >>>>> in this case, if swiotlb or DMA buffers are requierd, crash dump kernel >>>>> will boot failure because there is no low memory available for allocation. >>> >>> >>> Can you elaborate when the boot failures may fail due to lacking swiotlb or DMA buffers ? Are these related to certain adapters or specific platforms ? >>> >>> I have not seen this when using crashkernel=2024M@35GB . >>> >> >> For example, in my environment "Huawei TaiShan 2280", >> we need to use mpt3sas driver in crash dump kernel for dumping vmcore. >> >> mpt3sas driver needs to call dma_pool_alloc to allocate some pages, >> if there is no DMA buffer, page allocation will fail, which leads to crash dump kernel boot failure, >> like this: >> >> [2019/12/19 9:12:41] [ 12.403501] mpt3sas_cm0: diag reset: SUCCESS >> [2019/12/19 9:12:41] [ 12.456076] mpt3sas_cm0: reply_post_free pool: dma_pool_alloc failed >> [2019/12/19 9:12:41] [ 12.462515] pci 0004:48:00.0: can't derive routing for PCI INT A >> [2019/12/19 9:12:41] [ 12.468761] mpt3sas 0004:49:00.0: PCI INT A: no GSI >> [2019/12/19 9:12:41] [ 12.476348] mpt3sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:10626/_scsih_probe()! >> [2019/12/19 9:14:38] [ TIME ] Timed out waiting for device dev-di…b3\x2d890a\x2d2ead7df26f48.device. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for Initrd Root Device. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for /sysroot. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for Initrd Root File System. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for Reload Configuration from the Real Root. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for File System C…40bae-9eb8-46b3-890a-2ead7df26f48. > > > Thank you for sharing . We are not seeing this issue on a 5.4.0.rc8 ; Like I said in a previous email we can take crash dumps using crashkernel=768M for a “ standard “ small VMcore to local storage : > > 0004:01:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3316 [Intruder] (rev 01) > Subsystem: Broadcom / LSI MegaRAID SAS 9361-16i > Kernel driver in use: megaraid_sas > > > What version of the kernel are you using ? 5.5.0.rc1 As I said in the patch series cover-letter, this patch series address following cases/isssues. There are following issues in arm64 kdump: 1. We use crashkernel=X to reserve crashkernel below 4G, which will fail when there is no enough low memory. 2. Currently, crashkernel=Y@X can be used to reserve crashkernel above 4G, in this case, if swiotlb or DMA buffers are required, crash dump kernel will boot failure because there is no low memory available for allocation. From your description, you use crashkernel=768M. There are enough crashkernel below 4G, so crashkernel will be reserved successfully and kdump be ok. (This case has no DMA buffers issue.) or you use crashkernel=2024M@35GB, and this case is ok? If your driver doesn't need DMA buffers(I am not sure about it), kdump will also be ok. If i understand your question and explain clearly? Thanks, Chen Zhou > > >> >> Thanks, >> Chen Zhou >> >>> >>>>> >>>>> To solve these issues, introduce crashkernel=X,low to reserve specified >>>>> size low memory. >>>>> Crashkernel=X tries to reserve memory for the crash dump kernel under >>>>> 4G. If crashkernel=Y,low is specified simultaneously, reserve spcified >>>>> size low memory for crash kdump kernel devices firstly and then reserve >>>>> memory above 4G. >>>>> >>>>> When crashkernel is reserved above 4G in memory, that is, crashkernel=X,low >>>>> is specified simultaneously, kernel should reserve specified size low memory >>>>> for crash dump kernel devices. So there may be two crash kernel regions, one >>>>> is below 4G, the other is above 4G. >>>>> In order to distinct from the high region and make no effect to the use of >>>>> kexec-tools, rename the low region as "Crash kernel (low)", and add DT property >>>>> "linux,low-memory-range" to crash dump kernel's dtb to pass the low region. >>>>> >>>>> Besides, we need to modify kexec-tools: >>>>> arm64: kdump: add another DT property to crash dump kernel's dtb(see [1]) >>>>> >>>>> The previous changes and discussions can be retrieved from: >>>>> >>>>> Changes since [v5] >>>>> - Move reserve_crashkernel_low() into kernel/crash_core.c. >>>>> - Delete crashkernel=X,high. >>>>> - Modify crashkernel=X,low. >>>>> If crashkernel=X,low is specified simultaneously, reserve spcified size low >>>>> memory for crash kdump kernel devices firstly and then reserve memory above 4G. >>>>> In addition, rename crashk_low_res as "Crash kernel (low)" for arm64, and then >>>>> pass to crash dump kernel by DT property "linux,low-memory-range". >>>>> - Update Documentation/admin-guide/kdump/kdump.rst. >>>>> >>>>> Changes since [v4] >>>>> - Reimplement memblock_cap_memory_ranges for multiple ranges by Mike. >>>>> >>>>> Changes since [v3] >>>>> - Add memblock_cap_memory_ranges back for multiple ranges. >>>>> - Fix some compiling warnings. >>>>> >>>>> Changes since [v2] >>>>> - Split patch "arm64: kdump: support reserving crashkernel above 4G" as >>>>> two. Put "move reserve_crashkernel_low() into kexec_core.c" in a separate >>>>> patch. >>>>> >>>>> Changes since [v1]: >>>>> - Move common reserve_crashkernel_low() code into kernel/kexec_core.c. >>>>> - Remove memblock_cap_memory_ranges() i added in v1 and implement that >>>>> in fdt_enforce_memory_region(). >>>>> There are at most two crash kernel regions, for two crash kernel regions >>>>> case, we cap the memory range [min(regs[*].start), max(regs[*].end)] >>>>> and then remove the memory range in the middle. >>>>> >>>>> [1]: https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_pipermail_kexec_2019-2DAugust_023569.html&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=9tn9kUBabiuYhVtXauANSDGaISnCnHLYcAUQgsPBFxs&e= >>>>> [v1]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_2_1174&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=F-lM7II2cuMF_sK3b6-QhSbWM3X-pI_WZEs0sZitS7A&e= >>>>> [v2]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_9_86&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=5Y-S6sqMTklHkOQsNtjTX3C7pV05BjKLGhJVfMHEvDs&e= >>>>> [v3]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_9_306&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=cWn4zSRQupaZ3jjz4eDvD-pNkoLyL_hsZoRx4yJoD0c&e= >>>>> [v4]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_15_273&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=Nslk4RJKIyIuT0IoQoolXNjupEDXplPhQQwnTSoXNWE&e= >>>>> [v5]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_5_6_1360&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=HJVAM6sCxV2DnNg5d4pw8WPqtkmQnKvztEmkSIgtQ5M&e= >>>>> >>>>> Chen Zhou (4): >>>>> x86: kdump: move reserve_crashkernel_low() into crash_core.c >>>>> arm64: kdump: reserve crashkenel above 4G for crash dump kernel >>>>> arm64: kdump: add memory for devices by DT property, low-memory-range >>>>> kdump: update Documentation about crashkernel on arm64 >>>>> >>>>> Documentation/admin-guide/kdump/kdump.rst | 13 ++++- >>>>> Documentation/admin-guide/kernel-parameters.txt | 12 ++++- >>>>> arch/arm64/include/asm/kexec.h | 3 ++ >>>>> arch/arm64/kernel/setup.c | 8 ++- >>>>> arch/arm64/mm/init.c | 61 +++++++++++++++++++++-- >>>>> arch/x86/include/asm/kexec.h | 3 ++ >>>>> arch/x86/kernel/setup.c | 65 +++---------------------- >>>>> include/linux/crash_core.h | 4 ++ >>>>> include/linux/kexec.h | 1 - >>>>> kernel/crash_core.c | 65 +++++++++++++++++++++++++ >>>>> 10 files changed, 168 insertions(+), 67 deletions(-) >>>>> >>>> >>>> >>>> _______________________________________________ >>>> kexec mailing list >>>> kexec@lists.infradead.org >>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_mailman_listinfo_kexec&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=XMcFx61B_QPg-FUfG_-t88DKCnGm4grqu6zRguiHYrU&e= >>> >>> >>> . > > > . >
WARNING: multiple messages have this Message-ID (diff)
From: Chen Zhou <chenzhou10@huawei.com> To: John Donnelly <john.p.donnelly@oracle.com> Cc: horms@verge.net.au, will@kernel.org, catalin.marinas@arm.com, bhsharma@redhat.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, mingo@redhat.com, james.morse@arm.com, guohanjun@huawei.com, tglx@linutronix.de, dyoung@redhat.com, linux-arm-kernel@lists.infradead.org Subject: Re: ` Date: Fri, 20 Dec 2019 09:44:52 +0800 [thread overview] Message-ID: <f8f5f7ae-718f-a411-26ff-999b0620dbce@huawei.com> (raw) In-Reply-To: <EA397BBF-56F6-4E8A-964D-ACB78F1DD9B4@oracle.com> Hi John, On 2019/12/20 2:33, John Donnelly wrote: > > >> On Dec 18, 2019, at 8:56 PM, Chen Zhou <chenzhou10@huawei.com> wrote: >> >> Hi John, >> >> On 2019/12/19 1:18, John Donnelly wrote: >>> HI >>> >>> SEE INLINE ON A QUESTION : >>> >>>> On Dec 17, 2019, at 8:07 PM, Chen Zhou <chenzhou10@huawei.com> wrote: >>>> >>>> Hi all, >>>> >>>> Friendly ping... >>>> >>>> On 2019/8/30 15:11, Chen Zhou wrote: >>>>> I am busy with other things, so it was a long time before this version was >>>>> released. >>>>> >>>>> This patch series enable reserving crashkernel above 4G in arm64. >>>>> >>>>> There are following issues in arm64 kdump: >>>>> 1. We use crashkernel=X to reserve crashkernel below 4G, which will fail >>>>> when there is no enough low memory. >>>>> 2. Currently, crashkernel=Y@X can be used to reserve crashkernel above 4G, >>>>> in this case, if swiotlb or DMA buffers are requierd, crash dump kernel >>>>> will boot failure because there is no low memory available for allocation. >>> >>> >>> Can you elaborate when the boot failures may fail due to lacking swiotlb or DMA buffers ? Are these related to certain adapters or specific platforms ? >>> >>> I have not seen this when using crashkernel=2024M@35GB . >>> >> >> For example, in my environment "Huawei TaiShan 2280", >> we need to use mpt3sas driver in crash dump kernel for dumping vmcore. >> >> mpt3sas driver needs to call dma_pool_alloc to allocate some pages, >> if there is no DMA buffer, page allocation will fail, which leads to crash dump kernel boot failure, >> like this: >> >> [2019/12/19 9:12:41] [ 12.403501] mpt3sas_cm0: diag reset: SUCCESS >> [2019/12/19 9:12:41] [ 12.456076] mpt3sas_cm0: reply_post_free pool: dma_pool_alloc failed >> [2019/12/19 9:12:41] [ 12.462515] pci 0004:48:00.0: can't derive routing for PCI INT A >> [2019/12/19 9:12:41] [ 12.468761] mpt3sas 0004:49:00.0: PCI INT A: no GSI >> [2019/12/19 9:12:41] [ 12.476348] mpt3sas_cm0: failure at drivers/scsi/mpt3sas/mpt3sas_scsih.c:10626/_scsih_probe()! >> [2019/12/19 9:14:38] [ TIME ] Timed out waiting for device dev-di…b3\x2d890a\x2d2ead7df26f48.device. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for Initrd Root Device. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for /sysroot. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for Initrd Root File System. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for Reload Configuration from the Real Root. >> [2019/12/19 9:14:38] [DEPEND] Dependency failed for File System C…40bae-9eb8-46b3-890a-2ead7df26f48. > > > Thank you for sharing . We are not seeing this issue on a 5.4.0.rc8 ; Like I said in a previous email we can take crash dumps using crashkernel=768M for a “ standard “ small VMcore to local storage : > > 0004:01:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3316 [Intruder] (rev 01) > Subsystem: Broadcom / LSI MegaRAID SAS 9361-16i > Kernel driver in use: megaraid_sas > > > What version of the kernel are you using ? 5.5.0.rc1 As I said in the patch series cover-letter, this patch series address following cases/isssues. There are following issues in arm64 kdump: 1. We use crashkernel=X to reserve crashkernel below 4G, which will fail when there is no enough low memory. 2. Currently, crashkernel=Y@X can be used to reserve crashkernel above 4G, in this case, if swiotlb or DMA buffers are required, crash dump kernel will boot failure because there is no low memory available for allocation. From your description, you use crashkernel=768M. There are enough crashkernel below 4G, so crashkernel will be reserved successfully and kdump be ok. (This case has no DMA buffers issue.) or you use crashkernel=2024M@35GB, and this case is ok? If your driver doesn't need DMA buffers(I am not sure about it), kdump will also be ok. If i understand your question and explain clearly? Thanks, Chen Zhou > > >> >> Thanks, >> Chen Zhou >> >>> >>>>> >>>>> To solve these issues, introduce crashkernel=X,low to reserve specified >>>>> size low memory. >>>>> Crashkernel=X tries to reserve memory for the crash dump kernel under >>>>> 4G. If crashkernel=Y,low is specified simultaneously, reserve spcified >>>>> size low memory for crash kdump kernel devices firstly and then reserve >>>>> memory above 4G. >>>>> >>>>> When crashkernel is reserved above 4G in memory, that is, crashkernel=X,low >>>>> is specified simultaneously, kernel should reserve specified size low memory >>>>> for crash dump kernel devices. So there may be two crash kernel regions, one >>>>> is below 4G, the other is above 4G. >>>>> In order to distinct from the high region and make no effect to the use of >>>>> kexec-tools, rename the low region as "Crash kernel (low)", and add DT property >>>>> "linux,low-memory-range" to crash dump kernel's dtb to pass the low region. >>>>> >>>>> Besides, we need to modify kexec-tools: >>>>> arm64: kdump: add another DT property to crash dump kernel's dtb(see [1]) >>>>> >>>>> The previous changes and discussions can be retrieved from: >>>>> >>>>> Changes since [v5] >>>>> - Move reserve_crashkernel_low() into kernel/crash_core.c. >>>>> - Delete crashkernel=X,high. >>>>> - Modify crashkernel=X,low. >>>>> If crashkernel=X,low is specified simultaneously, reserve spcified size low >>>>> memory for crash kdump kernel devices firstly and then reserve memory above 4G. >>>>> In addition, rename crashk_low_res as "Crash kernel (low)" for arm64, and then >>>>> pass to crash dump kernel by DT property "linux,low-memory-range". >>>>> - Update Documentation/admin-guide/kdump/kdump.rst. >>>>> >>>>> Changes since [v4] >>>>> - Reimplement memblock_cap_memory_ranges for multiple ranges by Mike. >>>>> >>>>> Changes since [v3] >>>>> - Add memblock_cap_memory_ranges back for multiple ranges. >>>>> - Fix some compiling warnings. >>>>> >>>>> Changes since [v2] >>>>> - Split patch "arm64: kdump: support reserving crashkernel above 4G" as >>>>> two. Put "move reserve_crashkernel_low() into kexec_core.c" in a separate >>>>> patch. >>>>> >>>>> Changes since [v1]: >>>>> - Move common reserve_crashkernel_low() code into kernel/kexec_core.c. >>>>> - Remove memblock_cap_memory_ranges() i added in v1 and implement that >>>>> in fdt_enforce_memory_region(). >>>>> There are at most two crash kernel regions, for two crash kernel regions >>>>> case, we cap the memory range [min(regs[*].start), max(regs[*].end)] >>>>> and then remove the memory range in the middle. >>>>> >>>>> [1]: https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_pipermail_kexec_2019-2DAugust_023569.html&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=9tn9kUBabiuYhVtXauANSDGaISnCnHLYcAUQgsPBFxs&e= >>>>> [v1]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_2_1174&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=F-lM7II2cuMF_sK3b6-QhSbWM3X-pI_WZEs0sZitS7A&e= >>>>> [v2]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_9_86&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=5Y-S6sqMTklHkOQsNtjTX3C7pV05BjKLGhJVfMHEvDs&e= >>>>> [v3]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_9_306&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=cWn4zSRQupaZ3jjz4eDvD-pNkoLyL_hsZoRx4yJoD0c&e= >>>>> [v4]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_4_15_273&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=Nslk4RJKIyIuT0IoQoolXNjupEDXplPhQQwnTSoXNWE&e= >>>>> [v5]: https://urldefense.proofpoint.com/v2/url?u=https-3A__lkml.org_lkml_2019_5_6_1360&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=HJVAM6sCxV2DnNg5d4pw8WPqtkmQnKvztEmkSIgtQ5M&e= >>>>> >>>>> Chen Zhou (4): >>>>> x86: kdump: move reserve_crashkernel_low() into crash_core.c >>>>> arm64: kdump: reserve crashkenel above 4G for crash dump kernel >>>>> arm64: kdump: add memory for devices by DT property, low-memory-range >>>>> kdump: update Documentation about crashkernel on arm64 >>>>> >>>>> Documentation/admin-guide/kdump/kdump.rst | 13 ++++- >>>>> Documentation/admin-guide/kernel-parameters.txt | 12 ++++- >>>>> arch/arm64/include/asm/kexec.h | 3 ++ >>>>> arch/arm64/kernel/setup.c | 8 ++- >>>>> arch/arm64/mm/init.c | 61 +++++++++++++++++++++-- >>>>> arch/x86/include/asm/kexec.h | 3 ++ >>>>> arch/x86/kernel/setup.c | 65 +++---------------------- >>>>> include/linux/crash_core.h | 4 ++ >>>>> include/linux/kexec.h | 1 - >>>>> kernel/crash_core.c | 65 +++++++++++++++++++++++++ >>>>> 10 files changed, 168 insertions(+), 67 deletions(-) >>>>> >>>> >>>> >>>> _______________________________________________ >>>> kexec mailing list >>>> kexec@lists.infradead.org >>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.infradead.org_mailman_listinfo_kexec&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=ZAC6UYbT-3qLR3Dvevd09m6neWWzGWSphuvXXlXow68&s=XMcFx61B_QPg-FUfG_-t88DKCnGm4grqu6zRguiHYrU&e= >>> >>> >>> . > > > . > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-20 1:45 UTC|newest] Thread overview: 206+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-08-30 7:11 [PATCH v6 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-30 7:11 ` [PATCH v6 1/4] x86: kdump: move reserve_crashkernel_low() into crash_core.c Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-31 23:12 ` kbuild test robot 2019-08-31 23:12 ` kbuild test robot 2019-08-31 23:12 ` kbuild test robot 2019-08-31 23:48 ` kbuild test robot 2019-08-31 23:48 ` kbuild test robot 2019-08-31 23:48 ` kbuild test robot 2019-08-30 7:11 ` [PATCH v6 2/4] arm64: kdump: reserve crashkenel above 4G for crash dump kernel Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-30 7:11 ` [PATCH v6 3/4] arm64: kdump: add memory for devices by DT property, low-memory-range Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-30 7:11 ` Chen Zhou 2019-08-30 7:12 ` [PATCH v6 4/4] kdump: update Documentation about crashkernel on arm64 Chen Zhou 2019-08-30 7:12 ` Chen Zhou 2019-08-30 7:12 ` Chen Zhou 2019-12-18 2:07 ` [PATCH v6 0/4] support reserving crashkernel above 4G on arm64 kdump Chen Zhou 2019-12-18 2:07 ` Chen Zhou 2019-12-18 2:07 ` Chen Zhou 2019-12-18 9:09 ` Will Deacon 2019-12-18 9:09 ` Will Deacon 2019-12-18 9:09 ` Will Deacon 2019-12-19 1:35 ` Chen Zhou 2019-12-19 1:35 ` Chen Zhou 2019-12-19 1:35 ` Chen Zhou 2019-12-18 16:21 ` John Donnelly 2019-12-18 17:18 ` John Donnelly 2019-12-18 17:18 ` John Donnelly 2019-12-18 17:18 ` John Donnelly 2019-12-19 2:56 ` Chen Zhou 2019-12-19 2:56 ` Chen Zhou 2019-12-19 2:56 ` Chen Zhou 2019-12-19 18:33 ` ` John Donnelly 2019-12-20 1:44 ` Chen Zhou [this message] 2019-12-20 1:44 ` ` Chen Zhou -- strict thread matches above, loose matches on Subject: below -- 2024-03-16 11:59 👍 Sophia Wang 2021-03-21 17:01 [PATCH net-next 0/8] udp: GRO L4 improvements Paolo Abeni 2021-03-21 17:01 ` [PATCH net-next 2/8] udp: skip fwd/list GRO for tunnel packets Paolo Abeni 2021-03-22 13:24 ` Willem de Bruijn 2021-03-22 16:41 ` Paolo Abeni 2021-03-24 1:54 ` Willem de Bruijn 2021-03-24 14:50 ` ! Paolo Abeni 2021-03-24 22:45 ` ! Willem de Bruijn 2021-02-04 13:17 [] Joachim Wiberg 2021-02-04 13:58 ` [] Joachim Wiberg 2020-04-29 13:32 [PATCH v3 2/5] w1_therm: adding sysfs entry to check device power Akira Shimahara 2020-04-29 13:46 ` Greg KH 2020-04-29 13:57 ` _ Akira shimahara 2019-10-15 16:34 👑 sunil saraff 2019-08-30 18:30 👆 nik_bin_nek_alwi 2019-05-06 10:07 ? Ms Ella Golan 2018-03-28 21:39 ÈçºÎËõ¶ÌÉú²úÖÜÆÚ£¬×¼Ê±½»»õºÍ½µµÍ¿â´æ ÏòÔóÌì 2018-03-27 8:48 ÖÐ ²ã ¸É ²¿ Èç ºÎµ± ÔÆÃî÷ë 2017-10-17 8:40 ¿À´Ã ±ÞµîÁÖ ¾îÁ¦ ¾î¶»°Ô ¾Ë¾ÒÀ»±î¿ä? µµ³Îµå Æ®·³ÇÁ 2017-09-13 2:46 ÁÖ½Ä Å¬·´ ȸ¿øºÐµé²² Èñ¼Ò½ÄÀÖ¾î °øÀ¯Çմϴ٠Ŭ·´Àå 2017-08-19 12:11 Ó²¼þµç·Éè¼Æ¡¢¹ÊÕ϶¨Î»Ó빤³Ì°¸Àý·ÖÎö Òüƽ½¨ 2017-08-18 20:06 ÈçºÎ¹æ»®²úƷƽ̨£¿ÈçºÎ½øÐм¼Êõ¹æ»®£¿ ÁÎêØÓÑ 2017-08-18 3:06 ´ÓÖ»¶Ô¼¼Êõ¸ºÔðת±äΪ¶ÔÈ«Á÷³Ì¸ºÔð Æֵϰ® 2017-07-23 17:29 ? Robert 2017-07-23 17:09 ? Robert 2017-07-23 17:09 ? Robert 2017-07-10 17:16 »Ø¸´£ºÈçºÎ±ÜÃâ²ú Æ·¾ÀíÂÙÂä³É"ÎÊÌâ¾Àí"£¿ Ï¿ 2017-07-10 17:02 ת·¢£ºÌá¸ß²úÆ·µÄÖÊÁ¿£¬ÌáÉý²úÆ·µÄ¾ºÕùÁ¦£¬È·±£Êг¡³É¹¦ Ò¶ÄþÒä 2017-05-29 4:56 [±¤°í] Áö±ÝÀº ¼ÒÇü Ä«Æä â¾÷ ½Ã´ë ¹Ú °úÀå 2016-12-26 21:03 ???????????????? nd 2016-12-18 13:16 ??????????????? ??? 2016-11-15 20:29 Christoph Lameter 2016-11-15 21:58 ` ??? Steven Rostedt 2016-11-11 3:38 Chunyan Zhang 2016-11-11 16:01 ` ?? Steven Rostedt 2016-11-11 16:01 ` ?? Steven Rostedt [not found] <CAHjEeniVr6YmfLojEJutcEqk1pX0jTOvFvtJs4WvxQC2bJ4C3g@mail.gmail.com> 2016-06-01 1:13 ` ###$$$@# iutititbpigi 2016-05-07 21:24 ? Robert [not found] <CAP9ngMJVJuqWMsfRNTaVQk_2690m1Vic60SRXOb8dzg9i=KEMA@mail.gmail.com> 2015-10-27 20:39 ` ? Amall 2015-09-29 15:58 ! Kathrine 2015-08-01 12:29 ! Rita 2015-08-01 8:50 ! Rita 2015-04-04 5:40 Old regression with MTD devices disappearing from a Kurobox HD/HG Rogério Brito 2015-04-07 22:34 ` Scott Wood 2015-04-07 23:58 ` Rogério Brito 2015-04-08 0:02 ` Scott Wood 2015-04-08 0:37 ` Rogério Brito 2015-04-08 0:50 ` Scott Wood 2015-04-08 1:13 ` Rogério Brito 2015-04-08 1:27 ` ) Scott Wood 2014-12-13 6:29 $ FBI 2014-08-29 15:55 ? Kristofer Hallin 2014-08-29 16:03 ` ? Ravi Raj 2014-08-29 16:13 ` ? Bjørn Mork 2014-08-29 16:43 ` ? Valdis.Kletnieks at vt.edu 2014-08-29 17:18 ` ? Ravi Raj 2014-06-02 17:31 =================== Amanda Clarke 2014-03-21 4:50 # # Ausilia Alessi 2013-11-23 0:47 ?? seyed.jamaly 2013-11-07 4:57 ?? jjorge 2013-10-19 7:26 ! Ana Flavia Maria 2013-10-19 7:26 ` ! Ana Flavia Maria 2013-09-25 12:01 $ FBI 2013-08-09 20:55 : JOEL SULLINS 2012-12-18 4:19 ^……――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――####################・・・・・・・・・・・・・・・・・・・・・・・・・・・・・・・・・・・・ farm228694 [not found] <1450527224.97.1352925325502.JavaMail.root@thunderbeast.private.linuxbox.com> 2012-11-14 20:38 ` ! Matt W. Benjamin 2012-11-14 21:03 ` ! Myklebust, Trond 2012-11-14 20:13 xattr support in NFS? Matt W. Benjamin 2012-11-14 20:24 ` ! Myklebust, Trond 2012-09-28 5:01 ãîðÿ÷àÿ Àíýëÿ õî÷åò ïîùóïàòü âàñ!!!!! polesky 2012-08-25 7:06 $ Xli 2012-08-25 7:06 $ Xli 2012-08-25 7:06 $ Xli 2012-08-25 7:06 $ Xli 2012-08-25 7:06 ` $ Xli 2012-08-25 7:06 ` $ Xli 2012-08-25 7:06 $ Xli 2012-08-25 7:06 $ Xli-yEtiT0l5D7D2fBVCVOL8/A 2012-08-25 6:42 $ Xli 2012-08-25 6:42 $ Xli 2012-04-26 23:47 ((((= Анночка Парамонова 2012-01-01 12:45 ! FBI 2011-10-31 17:58 ! FBI 2011-09-29 16:20 ! FBI 2011-02-16 10:17 $ Sgt Moore Paul 2011-01-03 13:45 $ Sgt Moore Paul 2010-11-16 13:59 , Ming-Yang Lee 2010-07-27 7:46 , john erchart 2010-07-24 7:48 , Mr.COOK ADAMS 2010-06-28 4:59 section .data..init_task Sean MacLennan 2010-07-13 0:34 ` Sean MacLennan 2010-07-13 9:50 ` [ Sam Ravnborg 2010-07-22 22:27 ` [ Sean MacLennan 2010-07-22 22:33 ` [ Benjamin Herrenschmidt 2010-06-27 18:43 , Mr.COOK ADAMS 2010-06-27 18:01 , Mr.COOK ADAMS 2010-06-27 11:02 , DHL UNIT 2010-06-16 20:30 , SBECKFORD Financial Loan Company 2010-06-16 18:57 , SBECKFORD Financial Loan Company 2010-06-12 9:59 , Mr.COOK ADAMS 2010-05-30 14:19 [PATCH 0/6] mips: diverse Makefile updates Sam Ravnborg 2010-05-30 18:03 ` [ Sam Ravnborg 2010-02-22 20:25 , JOSE LOANS 2010-02-22 18:39 , JOSE LOANS 2010-02-22 18:17 , JOSE LOANS 2010-02-22 17:53 , JOSE LOANS 2008-07-15 19:46 :) Corsello Merchen 2008-03-28 23:48 + revert-gregkh-pci-pci-x86-use-generic-pci_enable_resources.patch added to -mm tree akpm 2008-04-01 15:57 ` Bjorn Helgaas 2008-04-01 17:00 ` + Andrew Morton 2008-04-01 20:38 ` + Benjamin Herrenschmidt 2008-04-01 20:37 ` + Benjamin Herrenschmidt 2008-04-02 5:15 ` + Greg KH 2008-04-02 14:43 ` + revert-gregkh-pci-pci-x86-use-generic-pci_enable_resources.patch added to -mm tree Bjorn Helgaas 2008-04-14 22:10 ` + Greg KH 2008-03-21 5:19 Âàø äîïîëíèòåëüíûé çàðàáîòîê,à âîçìîæíî è îáåñïå÷åííîå áóäóùåå Âëàäèìèð 2008-03-20 16:15 Âëàäèìèð 2008-03-18 7:55 Âëàäèìèð 2008-03-17 11:35 Âëàäèìèð 2008-03-13 17:11 Âëàäèìèð 2008-03-11 4:31 [PATCH] Move memory controller allocations to their own slabs Balbir Singh 2008-03-11 5:00 ` + KOSAKI Motohiro 2008-03-11 5:00 ` + KOSAKI Motohiro 2008-03-11 5:07 ` + Balbir Singh 2008-03-11 5:07 ` + Balbir Singh 2008-03-07 0:33 Âàø äîïîëíèòåëüíûé äîõîä,à ìîæåò è îáåñïå÷åííîå áóäóùåå Âëàäèìèð 2007-10-29 14:44 àúí îöìîéí àú äö'÷éí? àé ãé ôé îåöøé æéäåé àì÷èøåðééí 2007-10-22 6:47 àé ãé ôé îåöøé æéäåé àì÷èøåðééí 2007-10-01 2:45 äæîï ùìê é÷ø? àé ãé ôé îåöøé æéäåé àì÷èøåðééí 2007-09-21 13:14 àé ãé ôé îåöøé æéäåé àì÷èøåðééí 2007-09-19 11:37 äæîï ùìê é÷ø IDP 2007-09-18 20:50 ) !)!)++[(] *)()! Steven Maddox 2007-09-17 14:07 ) +( )(:+!: [!** Lena Pena 2007-08-25 19:05 çñåê æîï åèòåéåú I.D.P 2007-08-17 17:57 àðé ìà æåëø àú ëì äôøèéí àé ãé ôé 2007-04-12 20:01 [PATCH] FC Transport support for vports based on NPIV James Smart 2007-05-14 12:12 ` Christof Schmitt 2007-05-14 15:56 ` ` James Smart 2007-01-08 23:27 + Andrew Morton 2007-01-09 0:16 ` + Andrew Morton 2006-09-29 21:42 ? Jane Stevens 2006-08-17 20:14 îçùá ëó éã áîúðä áæ÷ ìòñ÷éí 2006-07-23 20:20 øåöä ìäøùéí àú äì÷åç ùìê ? ìéàú 2006-07-04 12:43 øåöä ìäéåú îìê ìéåí àçã ? ìéàú [not found] <29030224173406.A16366@crowberry.doit.wisc.edu> [not found] ` <22731128143048.B6094@cancelled.doit.wisc.edu> 2006-05-19 5:55 ` ? Belinda Mclaughlin 2005-08-16 5:35 çåùáéí òì úåàø ùðé? ìçöå ëàï ìäöòä ùìà úçæåø áùðéú ìéãåø ù 2005-07-18 8:15 áòì òñ÷! òì ëîä ì÷åçåú àúä îåëï ìååúø? ëôéø 2005-07-09 12:37 çåùáéí òì úåàø ùðé? ìçöå ëàï ìäöòä ùìà úçæåø áùðéú innovate 2005-07-02 20:21 îìâåú ééçåãéåú ìðøùîéí òëùéå ìúåàø ùðé innovate 2005-06-18 4:30 áåàå ìäùìéí " éåñé 2005-06-17 16:00 àúä çééá àú æä ìòöîê yuval 2004-11-07 14:04 =\ Alan Grimes 2004-09-30 2:19 ??? Charlie LaMothe 2004-09-08 9:57 îîðé áàäáä Myluck 2004-05-07 10:07 :) majordomo 2004-05-06 15:12 :) becker 2004-04-06 15:54 :) webmaster 2003-07-07 16:38 (±¤°í)ÀÎÅͳݺξ÷ ±è¿øº¹ 2003-04-28 11:42 (±¤°í)½Å±Ôâ¾÷, Áß¼Ò±â¾÷, µµ¼Ò¸Å À¯Åë¾÷ ÃÖÀû¼Ö·ç¼Ç Åä¹Ì½Ã½ºÅÛ °ü¸®ÀÚ 2003-04-25 15:48 :((((((( Balram Adlakha 2003-04-25 15:59 ` :((((((( CaT 2003-04-25 16:08 ` :((((((( Valdis.Kletnieks 2003-04-25 18:07 ` :((((((( Benjamin Herrenschmidt 2003-04-01 20:13 ? Soporte Meranetwork 2003-01-08 6:53 !?! Anton Erofeevskij 2003-01-08 7:18 ` !?! Russell Coker 2003-01-08 7:33 ` !?! Anton Erofeevskij 2003-01-08 15:38 ` !?! Anton Erofeevskij 2003-01-09 6:40 ` !?! Oleg Drokin 2002-03-31 13:25 [±¤** °í]º»¸ÞÀÏÀº Á¤º¸Åë½ÅºÎ ±Ç°í»çÇ׿¡ µû¶ó Á¦¸ñ¿¡ Ç¥±âÇÑ ¸ÞÀÏÀÔ´Ï´Ù ¿øÄ¡¾ÊÀ¸½ÅºÐÀº ¼ö½Å°ÅºÎ¸¦´·¯¼¸ÞÀÏÁÖ¼¼¿ä´Ù½Ãº¸³»Áö ¾Ê°Ú½À´Ï´Ù catsman 2002-04-01 3:02 ` [ Juan Linietsky 2002-02-17 2:11 \ Timothy Robinson 2002-02-05 23:48 äÌÑÇÌÁ×ÎÏÇÏÂÕÈÇÁÌÔÅÒÁ au_ru 2002-02-06 21:21 ` ????????????????????? Brian 2002-02-06 22:31 ` ????????????????????? Alex Bligh - linux-kernel 2002-02-06 22:46 ` ????????????????????? Roland Dreier 2002-02-07 11:12 ` ????????????????????? Bruce Harada 2002-02-07 19:59 ` ????????????????????? Pavel Machek 2002-02-06 23:42 ` ????????????????????? Brian 2002-02-07 11:44 ` ????????????????????? David S. Miller 2002-02-07 20:01 ` ????????????????????? Jesse Pollard 2002-02-08 9:57 ` ????????????????????? Horst von Brand 2002-02-07 12:12 ` ????????????????????? Pete Cervasio 2002-02-08 12:40 ` ????????????????????? Martin Dalecki 2002-02-07 12:47 ` ????????????????????? Oliver M . Bolzer 2001-12-30 22:40 [Ãßõ] ²À °ËÅäÇÏ¿© Áֽʽÿä news 2001-12-06 20:40 news [not found] <Pine.GSO.4.33.0110221628150.11349-100000@raven> 2001-10-22 20:49 ` ? Roberto Cescon 2001-10-22 20:30 ? Roberto Cescon 2000-06-19 17:06 [ Philippe Chauvat 2000-06-19 18:32 ` [ Florian Lohoff 2000-06-19 18:45 ` [ Keith M Wesolowski 2000-06-21 0:48 ` [ Ralf Baechle
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=f8f5f7ae-718f-a411-26ff-999b0620dbce@huawei.com \ --to=chenzhou10@huawei.com \ --cc=bhsharma@redhat.com \ --cc=catalin.marinas@arm.com \ --cc=dyoung@redhat.com \ --cc=guohanjun@huawei.com \ --cc=horms@verge.net.au \ --cc=james.morse@arm.com \ --cc=john.p.donnelly@oracle.com \ --cc=kexec@lists.infradead.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@redhat.com \ --cc=tglx@linutronix.de \ --cc=will@kernel.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.