From: Baoquan He <bhe@redhat.com>
To: kexec@lists.infradead.org
Subject: [PATCH v20 1/5] arm64: Use insert_resource() to simplify code
Date: Tue, 8 Feb 2022 09:43:07 +0800 [thread overview]
Message-ID: <YgHKq7o2Efb1JK7H@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220124084708.683-2-thunder.leizhen@huawei.com>
On 01/24/22 at 04:47pm, Zhen Lei wrote:
> insert_resource() traverses the subtree layer by layer from the root node
> until a proper location is found. Compared with request_resource(), the
> parent node does not need to be determined in advance.
>
> In addition, move the insertion of node 'crashk_res' into function
> reserve_crashkernel() to make the associated code close together.
This is nice cleanup.
Acked-by: Baoquan He <bhe@redhat.com>
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> arch/arm64/kernel/setup.c | 17 +++--------------
> arch/arm64/mm/init.c | 1 +
> 2 files changed, 4 insertions(+), 14 deletions(-)
>
> diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> index f70573928f1bff0..a81efcc359e4e78 100644
> --- a/arch/arm64/kernel/setup.c
> +++ b/arch/arm64/kernel/setup.c
> @@ -225,6 +225,8 @@ static void __init request_standard_resources(void)
> kernel_code.end = __pa_symbol(__init_begin - 1);
> kernel_data.start = __pa_symbol(_sdata);
> kernel_data.end = __pa_symbol(_end - 1);
> + insert_resource(&iomem_resource, &kernel_code);
> + insert_resource(&iomem_resource, &kernel_data);
>
> num_standard_resources = memblock.memory.cnt;
> res_size = num_standard_resources * sizeof(*standard_resources);
> @@ -246,20 +248,7 @@ static void __init request_standard_resources(void)
> res->end = __pfn_to_phys(memblock_region_memory_end_pfn(region)) - 1;
> }
>
> - request_resource(&iomem_resource, res);
> -
> - if (kernel_code.start >= res->start &&
> - kernel_code.end <= res->end)
> - request_resource(res, &kernel_code);
> - if (kernel_data.start >= res->start &&
> - kernel_data.end <= res->end)
> - request_resource(res, &kernel_data);
> -#ifdef CONFIG_KEXEC_CORE
> - /* Userspace will find "Crash kernel" region in /proc/iomem. */
> - if (crashk_res.end && crashk_res.start >= res->start &&
> - crashk_res.end <= res->end)
> - request_resource(res, &crashk_res);
> -#endif
> + insert_resource(&iomem_resource, res);
> }
> }
>
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index db63cc885771a52..90f276d46b93bc6 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -109,6 +109,7 @@ static void __init reserve_crashkernel(void)
> kmemleak_ignore_phys(crash_base);
> crashk_res.start = crash_base;
> crashk_res.end = crash_base + crash_size - 1;
> + insert_resource(&iomem_resource, &crashk_res);
> }
> #else
> static void __init reserve_crashkernel(void)
> --
> 2.25.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
kexec@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Feng Zhou <zhoufeng.zf@bytedance.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Chen Zhou <dingguo.cz@antgroup.com>,
John Donnelly <John.p.donnelly@oracle.com>,
Dave Kleikamp <dave.kleikamp@oracle.com>
Subject: Re: [PATCH v20 1/5] arm64: Use insert_resource() to simplify code
Date: Tue, 8 Feb 2022 09:43:07 +0800 [thread overview]
Message-ID: <YgHKq7o2Efb1JK7H@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220124084708.683-2-thunder.leizhen@huawei.com>
On 01/24/22 at 04:47pm, Zhen Lei wrote:
> insert_resource() traverses the subtree layer by layer from the root node
> until a proper location is found. Compared with request_resource(), the
> parent node does not need to be determined in advance.
>
> In addition, move the insertion of node 'crashk_res' into function
> reserve_crashkernel() to make the associated code close together.
This is nice cleanup.
Acked-by: Baoquan He <bhe@redhat.com>
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> arch/arm64/kernel/setup.c | 17 +++--------------
> arch/arm64/mm/init.c | 1 +
> 2 files changed, 4 insertions(+), 14 deletions(-)
>
> diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> index f70573928f1bff0..a81efcc359e4e78 100644
> --- a/arch/arm64/kernel/setup.c
> +++ b/arch/arm64/kernel/setup.c
> @@ -225,6 +225,8 @@ static void __init request_standard_resources(void)
> kernel_code.end = __pa_symbol(__init_begin - 1);
> kernel_data.start = __pa_symbol(_sdata);
> kernel_data.end = __pa_symbol(_end - 1);
> + insert_resource(&iomem_resource, &kernel_code);
> + insert_resource(&iomem_resource, &kernel_data);
>
> num_standard_resources = memblock.memory.cnt;
> res_size = num_standard_resources * sizeof(*standard_resources);
> @@ -246,20 +248,7 @@ static void __init request_standard_resources(void)
> res->end = __pfn_to_phys(memblock_region_memory_end_pfn(region)) - 1;
> }
>
> - request_resource(&iomem_resource, res);
> -
> - if (kernel_code.start >= res->start &&
> - kernel_code.end <= res->end)
> - request_resource(res, &kernel_code);
> - if (kernel_data.start >= res->start &&
> - kernel_data.end <= res->end)
> - request_resource(res, &kernel_data);
> -#ifdef CONFIG_KEXEC_CORE
> - /* Userspace will find "Crash kernel" region in /proc/iomem. */
> - if (crashk_res.end && crashk_res.start >= res->start &&
> - crashk_res.end <= res->end)
> - request_resource(res, &crashk_res);
> -#endif
> + insert_resource(&iomem_resource, res);
> }
> }
>
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index db63cc885771a52..90f276d46b93bc6 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -109,6 +109,7 @@ static void __init reserve_crashkernel(void)
> kmemleak_ignore_phys(crash_base);
> crashk_res.start = crash_base;
> crashk_res.end = crash_base + crash_size - 1;
> + insert_resource(&iomem_resource, &crashk_res);
> }
> #else
> static void __init reserve_crashkernel(void)
> --
> 2.25.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H . Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
kexec@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
Feng Zhou <zhoufeng.zf@bytedance.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Chen Zhou <dingguo.cz@antgroup.com>,
John Donnelly <John.p.donnelly@oracle.com>,
Dave Kleikamp <dave.kleikamp@oracle.com>
Subject: Re: [PATCH v20 1/5] arm64: Use insert_resource() to simplify code
Date: Tue, 8 Feb 2022 09:43:07 +0800 [thread overview]
Message-ID: <YgHKq7o2Efb1JK7H@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20220124084708.683-2-thunder.leizhen@huawei.com>
On 01/24/22 at 04:47pm, Zhen Lei wrote:
> insert_resource() traverses the subtree layer by layer from the root node
> until a proper location is found. Compared with request_resource(), the
> parent node does not need to be determined in advance.
>
> In addition, move the insertion of node 'crashk_res' into function
> reserve_crashkernel() to make the associated code close together.
This is nice cleanup.
Acked-by: Baoquan He <bhe@redhat.com>
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> arch/arm64/kernel/setup.c | 17 +++--------------
> arch/arm64/mm/init.c | 1 +
> 2 files changed, 4 insertions(+), 14 deletions(-)
>
> diff --git a/arch/arm64/kernel/setup.c b/arch/arm64/kernel/setup.c
> index f70573928f1bff0..a81efcc359e4e78 100644
> --- a/arch/arm64/kernel/setup.c
> +++ b/arch/arm64/kernel/setup.c
> @@ -225,6 +225,8 @@ static void __init request_standard_resources(void)
> kernel_code.end = __pa_symbol(__init_begin - 1);
> kernel_data.start = __pa_symbol(_sdata);
> kernel_data.end = __pa_symbol(_end - 1);
> + insert_resource(&iomem_resource, &kernel_code);
> + insert_resource(&iomem_resource, &kernel_data);
>
> num_standard_resources = memblock.memory.cnt;
> res_size = num_standard_resources * sizeof(*standard_resources);
> @@ -246,20 +248,7 @@ static void __init request_standard_resources(void)
> res->end = __pfn_to_phys(memblock_region_memory_end_pfn(region)) - 1;
> }
>
> - request_resource(&iomem_resource, res);
> -
> - if (kernel_code.start >= res->start &&
> - kernel_code.end <= res->end)
> - request_resource(res, &kernel_code);
> - if (kernel_data.start >= res->start &&
> - kernel_data.end <= res->end)
> - request_resource(res, &kernel_data);
> -#ifdef CONFIG_KEXEC_CORE
> - /* Userspace will find "Crash kernel" region in /proc/iomem. */
> - if (crashk_res.end && crashk_res.start >= res->start &&
> - crashk_res.end <= res->end)
> - request_resource(res, &crashk_res);
> -#endif
> + insert_resource(&iomem_resource, res);
> }
> }
>
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index db63cc885771a52..90f276d46b93bc6 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -109,6 +109,7 @@ static void __init reserve_crashkernel(void)
> kmemleak_ignore_phys(crash_base);
> crashk_res.start = crash_base;
> crashk_res.end = crash_base + crash_size - 1;
> + insert_resource(&iomem_resource, &crashk_res);
> }
> #else
> static void __init reserve_crashkernel(void)
> --
> 2.25.1
>
_______________________________________________
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:[~2022-02-08 1:43 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 8:47 [PATCH v20 0/5] support reserving crashkernel above 4G on arm64 kdump Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-24 8:47 ` [PATCH v20 1/5] arm64: Use insert_resource() to simplify code Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-26 15:16 ` john.p.donnelly
2022-01-26 15:16 ` john.p.donnelly
2022-01-26 15:16 ` john.p.donnelly
2022-02-08 1:43 ` Baoquan He [this message]
2022-02-08 1:43 ` Baoquan He
2022-02-08 1:43 ` Baoquan He
2022-01-24 8:47 ` [PATCH v20 2/5] arm64: kdump: introduce some macros for crash kernel reservation Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-26 15:17 ` john.p.donnelly
2022-01-26 15:17 ` john.p.donnelly
2022-01-26 15:17 ` john.p.donnelly
2022-02-11 10:39 ` Baoquan He
2022-02-11 10:39 ` Baoquan He
2022-02-11 10:39 ` Baoquan He
2022-02-14 6:22 ` Leizhen
2022-02-14 6:22 ` Leizhen (ThunderTown)
2022-02-14 6:22 ` Leizhen (ThunderTown)
2022-02-21 3:22 ` Baoquan He
2022-02-21 3:22 ` Baoquan He
2022-02-21 3:22 ` Baoquan He
2022-02-21 6:19 ` Leizhen
2022-02-21 6:19 ` Leizhen (ThunderTown)
2022-02-21 6:19 ` Leizhen (ThunderTown)
2022-01-24 8:47 ` [PATCH v20 3/5] arm64: kdump: reimplement crashkernel=X Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-26 15:18 ` john.p.donnelly
2022-01-26 15:18 ` john.p.donnelly
2022-01-26 15:18 ` john.p.donnelly
2022-02-11 10:30 ` Baoquan He
2022-02-11 10:30 ` Baoquan He
2022-02-11 10:30 ` Baoquan He
2022-02-11 10:41 ` Leizhen
2022-02-11 10:41 ` Leizhen (ThunderTown)
2022-02-11 10:41 ` Leizhen (ThunderTown)
2022-02-11 10:51 ` Baoquan He
2022-02-11 10:51 ` Baoquan He
2022-02-11 10:51 ` Baoquan He
2022-02-14 6:44 ` Leizhen
2022-02-14 6:44 ` Leizhen (ThunderTown)
2022-02-14 6:44 ` Leizhen (ThunderTown)
2022-02-14 7:09 ` Baoquan He
2022-02-14 7:09 ` Baoquan He
2022-02-14 7:09 ` Baoquan He
2022-02-14 3:52 ` Baoquan He
2022-02-14 3:52 ` Baoquan He
2022-02-14 3:52 ` Baoquan He
2022-02-14 7:53 ` Leizhen
2022-02-14 7:53 ` Leizhen (ThunderTown)
2022-02-14 7:53 ` Leizhen (ThunderTown)
2022-02-16 2:58 ` Leizhen
2022-02-16 2:58 ` Leizhen (ThunderTown)
2022-02-16 2:58 ` Leizhen (ThunderTown)
2022-02-16 10:20 ` Baoquan He
2022-02-16 10:20 ` Baoquan He
2022-02-16 10:20 ` Baoquan He
2022-02-17 1:57 ` Leizhen
2022-02-17 1:57 ` Leizhen (ThunderTown)
2022-02-17 1:57 ` Leizhen (ThunderTown)
2022-01-24 8:47 ` [PATCH v20 4/5] of: fdt: Add memory for devices by DT property "linux, usable-memory-range" Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-24 8:47 ` [PATCH v20 4/5] of: fdt: Add memory for devices by DT property "linux,usable-memory-range" Zhen Lei
2022-01-26 15:19 ` john.p.donnelly
2022-01-26 15:19 ` john.p.donnelly
2022-01-26 15:19 ` john.p.donnelly
2022-01-24 8:47 ` [PATCH v20 5/5] kdump: update Documentation about crashkernel Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-24 8:47 ` Zhen Lei
2022-01-26 15:19 ` john.p.donnelly
2022-01-26 15:19 ` john.p.donnelly
2022-01-26 15:19 ` john.p.donnelly
2022-02-21 3:48 ` Baoquan He
2022-02-21 3:48 ` Baoquan He
2022-02-21 3:48 ` Baoquan He
2022-02-21 6:38 ` Leizhen
2022-02-21 6:38 ` Leizhen (ThunderTown)
2022-02-21 6:38 ` Leizhen (ThunderTown)
2022-02-07 4:04 ` [PATCH v20 0/5] support reserving crashkernel above 4G on arm64 kdump Leizhen
2022-02-07 4:04 ` Leizhen (ThunderTown)
2022-02-07 4:04 ` Leizhen (ThunderTown)
2022-02-08 2:34 ` Baoquan He
2022-02-08 2:34 ` Baoquan He
2022-02-08 2:34 ` 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=YgHKq7o2Efb1JK7H@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=kexec@lists.infradead.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: link
Be 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.