| Message ID | 20230406220206.3067006-3-chenjiahao16@huawei.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | support allocating crashkernel above 4G explicitly on riscv | expand |
| Context | Check | Description |
|---|---|---|
| conchuod/cover_letter | success | Series has a cover letter |
| conchuod/tree_selection | success | Guessed tree name to be for-next at HEAD d34a6b715a23 |
| conchuod/fixes_present | success | Fixes tag not required for -next series |
| conchuod/maintainers_pattern | success | MAINTAINERS pattern errors before the patch: 1 and now 1 |
| conchuod/verify_signedoff | success | Signed-off-by tag matches author and committer |
| conchuod/kdoc | success | Errors and warnings before: 0 this patch: 0 |
| conchuod/build_rv64_clang_allmodconfig | success | Errors and warnings before: 18 this patch: 18 |
| conchuod/module_param | success | Was 0 now: 0 |
| conchuod/build_rv64_gcc_allmodconfig | success | Errors and warnings before: 18 this patch: 18 |
| conchuod/build_rv32_defconfig | success | Build OK |
| conchuod/dtb_warn_rv64 | success | Errors and warnings before: 3 this patch: 3 |
| conchuod/header_inline | success | No static functions without inline keyword in header files |
| conchuod/checkpatch | success | total: 0 errors, 0 warnings, 0 checks, 35 lines checked |
| conchuod/source_inline | success | Was 0 now: 0 |
| conchuod/build_rv64_nommu_k210_defconfig | success | Build OK |
| conchuod/verify_fixes | success | No Fixes tag |
| conchuod/build_rv64_nommu_virt_defconfig | success | Build OK |
Reviewed-by: Guo Ren <guoren@kernel.org> On Thu, Apr 6, 2023 at 10:05 PM Chen Jiahao <chenjiahao16@huawei.com> wrote: > > Now "crashkernel=" parameter on riscv has been updated to support > crashkernel=X,[high,low]. Through which we can reserve memory region > above/within 32bit addressible DMA zone. > > Here update the parameter description accordingly. > > Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com> > --- > Documentation/admin-guide/kernel-parameters.txt | 15 ++++++++------- > 1 file changed, 8 insertions(+), 7 deletions(-) > > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > index 54702bd488eb..41865aae9eaa 100644 > --- a/Documentation/admin-guide/kernel-parameters.txt > +++ b/Documentation/admin-guide/kernel-parameters.txt > @@ -866,7 +866,7 @@ > memory region [offset, offset + size] for that kernel > image. If '@offset' is omitted, then a suitable offset > is selected automatically. > - [KNL, X86-64, ARM64] Select a region under 4G first, and > + [KNL, X86-64, ARM64, RISCV] Select a region under 4G first, and > fall back to reserve region above 4G when '@offset' > hasn't been specified. > See Documentation/admin-guide/kdump/kdump.rst for further details. > @@ -879,14 +879,14 @@ > Documentation/admin-guide/kdump/kdump.rst for an example. > > crashkernel=size[KMG],high > - [KNL, X86-64, ARM64] range could be above 4G. Allow kernel > - to allocate physical memory region from top, so could > - be above 4G if system have more than 4G ram installed. > - Otherwise memory region will be allocated below 4G, if > - available. > + [KNL, X86-64, ARM64, RISCV] range could be above 4G. > + Allow kernel to allocate physical memory region from top, > + so could be above 4G if system have more than 4G ram > + installed. Otherwise memory region will be allocated > + below 4G, if available. > It will be ignored if crashkernel=X is specified. > crashkernel=size[KMG],low > - [KNL, X86-64, ARM64] range under 4G. When crashkernel=X,high > + [KNL, X86-64, ARM64, RISCV] range under 4G. When crashkernel=X,high > is passed, kernel could allocate physical memory region > above 4G, that cause second kernel crash on system > that require some amount of low memory, e.g. swiotlb > @@ -897,6 +897,7 @@ > size is platform dependent. > --> x86: max(swiotlb_size_or_default() + 8MiB, 256MiB) > --> arm64: 128MiB > + --> riscv: 128MiB > This one lets the user specify own low range under 4G > for second kernel instead. > 0: to disable low allocation. > -- > 2.31.1 >
On Fri, Apr 07, 2023 at 06:02:06AM +0800, Chen Jiahao wrote: > Now "crashkernel=" parameter on riscv has been updated to support > crashkernel=X,[high,low]. Through which we can reserve memory region > above/within 32bit addressible DMA zone. > > Here update the parameter description accordingly. > > Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com> Reviewed-by: Simon Horman <horms@kernel.org>
On 2023/4/7 6:02, Chen Jiahao wrote: > Now "crashkernel=" parameter on riscv has been updated to support > crashkernel=X,[high,low]. Through which we can reserve memory region > above/within 32bit addressible DMA zone. > > Here update the parameter description accordingly. Reviewed-by: Zhen Lei <thunder.leizhen@huawei.com> > > Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com> > --- > Documentation/admin-guide/kernel-parameters.txt | 15 ++++++++------- > 1 file changed, 8 insertions(+), 7 deletions(-) > > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt > index 54702bd488eb..41865aae9eaa 100644 > --- a/Documentation/admin-guide/kernel-parameters.txt > +++ b/Documentation/admin-guide/kernel-parameters.txt > @@ -866,7 +866,7 @@ > memory region [offset, offset + size] for that kernel > image. If '@offset' is omitted, then a suitable offset > is selected automatically. > - [KNL, X86-64, ARM64] Select a region under 4G first, and > + [KNL, X86-64, ARM64, RISCV] Select a region under 4G first, and > fall back to reserve region above 4G when '@offset' > hasn't been specified. > See Documentation/admin-guide/kdump/kdump.rst for further details. > @@ -879,14 +879,14 @@ > Documentation/admin-guide/kdump/kdump.rst for an example. > > crashkernel=size[KMG],high > - [KNL, X86-64, ARM64] range could be above 4G. Allow kernel > - to allocate physical memory region from top, so could > - be above 4G if system have more than 4G ram installed. > - Otherwise memory region will be allocated below 4G, if > - available. > + [KNL, X86-64, ARM64, RISCV] range could be above 4G. > + Allow kernel to allocate physical memory region from top, > + so could be above 4G if system have more than 4G ram > + installed. Otherwise memory region will be allocated > + below 4G, if available. > It will be ignored if crashkernel=X is specified. > crashkernel=size[KMG],low > - [KNL, X86-64, ARM64] range under 4G. When crashkernel=X,high > + [KNL, X86-64, ARM64, RISCV] range under 4G. When crashkernel=X,high > is passed, kernel could allocate physical memory region > above 4G, that cause second kernel crash on system > that require some amount of low memory, e.g. swiotlb > @@ -897,6 +897,7 @@ > size is platform dependent. > --> x86: max(swiotlb_size_or_default() + 8MiB, 256MiB) > --> arm64: 128MiB > + --> riscv: 128MiB > This one lets the user specify own low range under 4G > for second kernel instead. > 0: to disable low allocation. >
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index 54702bd488eb..41865aae9eaa 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -866,7 +866,7 @@ memory region [offset, offset + size] for that kernel image. If '@offset' is omitted, then a suitable offset is selected automatically. - [KNL, X86-64, ARM64] Select a region under 4G first, and + [KNL, X86-64, ARM64, RISCV] Select a region under 4G first, and fall back to reserve region above 4G when '@offset' hasn't been specified. See Documentation/admin-guide/kdump/kdump.rst for further details. @@ -879,14 +879,14 @@ Documentation/admin-guide/kdump/kdump.rst for an example. crashkernel=size[KMG],high - [KNL, X86-64, ARM64] range could be above 4G. Allow kernel - to allocate physical memory region from top, so could - be above 4G if system have more than 4G ram installed. - Otherwise memory region will be allocated below 4G, if - available. + [KNL, X86-64, ARM64, RISCV] range could be above 4G. + Allow kernel to allocate physical memory region from top, + so could be above 4G if system have more than 4G ram + installed. Otherwise memory region will be allocated + below 4G, if available. It will be ignored if crashkernel=X is specified. crashkernel=size[KMG],low - [KNL, X86-64, ARM64] range under 4G. When crashkernel=X,high + [KNL, X86-64, ARM64, RISCV] range under 4G. When crashkernel=X,high is passed, kernel could allocate physical memory region above 4G, that cause second kernel crash on system that require some amount of low memory, e.g. swiotlb @@ -897,6 +897,7 @@ size is platform dependent. --> x86: max(swiotlb_size_or_default() + 8MiB, 256MiB) --> arm64: 128MiB + --> riscv: 128MiB This one lets the user specify own low range under 4G for second kernel instead. 0: to disable low allocation.
Now "crashkernel=" parameter on riscv has been updated to support crashkernel=X,[high,low]. Through which we can reserve memory region above/within 32bit addressible DMA zone. Here update the parameter description accordingly. Signed-off-by: Chen Jiahao <chenjiahao16@huawei.com> --- Documentation/admin-guide/kernel-parameters.txt | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-)