From: Baoquan He <bhe@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Eric Biederman <ebiederm@xmission.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 4/6] kexec: improve the readability of crash_shrink_memory()
Date: Wed, 31 May 2023 15:48:30 +0800 [thread overview]
Message-ID: <ZHb7ubJYO2lyNkud@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230527123439.772-5-thunder.leizhen@huawei.com>
On 05/27/23 at 08:34pm, Zhen Lei wrote:
> The major adjustments are:
> 1. end = start + new_size.
> The 'end' here is not an accurate representation, because it is not the
> new end of crashk_res, but the start of ram_res, difference 1. So
> eliminate it and replace it with ram_res->start.
> 2. Use 'ram_res->start' and 'ram_res->end' as arguments to
> crash_free_reserved_phys_range() to indicate that the memory covered by
> 'ram_res' is released from the crashk. And keep it close to
> insert_resource().
> 3. Replace 'if (start == end)' with 'if (!new_size)', clear indication that
> all crashk memory will be shrunken.
>
> No functional change.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
LGTM,
Acked-by: Baoquan He <bhe@redhat.com>
> ---
> kernel/kexec_core.c | 15 +++++----------
> 1 file changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
> index bcc86a250ab3bf9..69fe92141b0b62d 100644
> --- a/kernel/kexec_core.c
> +++ b/kernel/kexec_core.c
> @@ -1108,7 +1108,6 @@ ssize_t crash_get_memory_size(void)
> int crash_shrink_memory(unsigned long new_size)
> {
> int ret = 0;
> - unsigned long start, end;
> unsigned long old_size;
> struct resource *ram_res;
>
> @@ -1119,9 +1118,7 @@ int crash_shrink_memory(unsigned long new_size)
> ret = -ENOENT;
> goto unlock;
> }
> - start = crashk_res.start;
> - end = crashk_res.end;
> - old_size = (end == 0) ? 0 : end - start + 1;
> + old_size = !crashk_res.end ? 0 : resource_size(&crashk_res);
> new_size = roundup(new_size, KEXEC_CRASH_MEM_ALIGN);
> if (new_size >= old_size) {
> ret = (new_size == old_size) ? 0 : -EINVAL;
> @@ -1134,22 +1131,20 @@ int crash_shrink_memory(unsigned long new_size)
> goto unlock;
> }
>
> - end = start + new_size;
> - crash_free_reserved_phys_range(end, crashk_res.end);
> -
> - ram_res->start = end;
> + ram_res->start = crashk_res.start + new_size;
> ram_res->end = crashk_res.end;
> ram_res->flags = IORESOURCE_BUSY | IORESOURCE_SYSTEM_RAM;
> ram_res->name = "System RAM";
>
> - if (start == end) {
> + if (!new_size) {
> release_resource(&crashk_res);
> crashk_res.start = 0;
> crashk_res.end = 0;
> } else {
> - crashk_res.end = end - 1;
> + crashk_res.end = ram_res->start - 1;
> }
>
> + crash_free_reserved_phys_range(ram_res->start, ram_res->end);
> insert_resource(&iomem_resource, ram_res);
>
> unlock:
> --
> 2.25.1
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Eric Biederman <ebiederm@xmission.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Michael Holzheu <holzheu@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 4/6] kexec: improve the readability of crash_shrink_memory()
Date: Wed, 31 May 2023 15:48:30 +0800 [thread overview]
Message-ID: <ZHb7ubJYO2lyNkud@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230527123439.772-5-thunder.leizhen@huawei.com>
On 05/27/23 at 08:34pm, Zhen Lei wrote:
> The major adjustments are:
> 1. end = start + new_size.
> The 'end' here is not an accurate representation, because it is not the
> new end of crashk_res, but the start of ram_res, difference 1. So
> eliminate it and replace it with ram_res->start.
> 2. Use 'ram_res->start' and 'ram_res->end' as arguments to
> crash_free_reserved_phys_range() to indicate that the memory covered by
> 'ram_res' is released from the crashk. And keep it close to
> insert_resource().
> 3. Replace 'if (start == end)' with 'if (!new_size)', clear indication that
> all crashk memory will be shrunken.
>
> No functional change.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
LGTM,
Acked-by: Baoquan He <bhe@redhat.com>
> ---
> kernel/kexec_core.c | 15 +++++----------
> 1 file changed, 5 insertions(+), 10 deletions(-)
>
> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
> index bcc86a250ab3bf9..69fe92141b0b62d 100644
> --- a/kernel/kexec_core.c
> +++ b/kernel/kexec_core.c
> @@ -1108,7 +1108,6 @@ ssize_t crash_get_memory_size(void)
> int crash_shrink_memory(unsigned long new_size)
> {
> int ret = 0;
> - unsigned long start, end;
> unsigned long old_size;
> struct resource *ram_res;
>
> @@ -1119,9 +1118,7 @@ int crash_shrink_memory(unsigned long new_size)
> ret = -ENOENT;
> goto unlock;
> }
> - start = crashk_res.start;
> - end = crashk_res.end;
> - old_size = (end == 0) ? 0 : end - start + 1;
> + old_size = !crashk_res.end ? 0 : resource_size(&crashk_res);
> new_size = roundup(new_size, KEXEC_CRASH_MEM_ALIGN);
> if (new_size >= old_size) {
> ret = (new_size == old_size) ? 0 : -EINVAL;
> @@ -1134,22 +1131,20 @@ int crash_shrink_memory(unsigned long new_size)
> goto unlock;
> }
>
> - end = start + new_size;
> - crash_free_reserved_phys_range(end, crashk_res.end);
> -
> - ram_res->start = end;
> + ram_res->start = crashk_res.start + new_size;
> ram_res->end = crashk_res.end;
> ram_res->flags = IORESOURCE_BUSY | IORESOURCE_SYSTEM_RAM;
> ram_res->name = "System RAM";
>
> - if (start == end) {
> + if (!new_size) {
> release_resource(&crashk_res);
> crashk_res.start = 0;
> crashk_res.end = 0;
> } else {
> - crashk_res.end = end - 1;
> + crashk_res.end = ram_res->start - 1;
> }
>
> + crash_free_reserved_phys_range(ram_res->start, ram_res->end);
> insert_resource(&iomem_resource, ram_res);
>
> unlock:
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-05-31 7:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 12:34 [PATCH 0/6] kexec: enable kexec_crash_size to support two crash kernel regions Zhen Lei
2023-05-27 12:34 ` Zhen Lei
2023-05-27 12:34 ` [PATCH 1/6] kexec: fix a memory leak in crash_shrink_memory() Zhen Lei
2023-05-27 12:34 ` Zhen Lei
2023-05-31 0:13 ` Baoquan He
2023-05-31 0:13 ` Baoquan He
2023-05-31 1:16 ` Leizhen (ThunderTown)
2023-05-31 1:16 ` Leizhen (ThunderTown)
2023-05-31 7:31 ` Baoquan He
2023-05-31 7:31 ` Baoquan He
2023-05-27 12:34 ` [PATCH 2/6] kexec: delete a useless check " Zhen Lei
2023-05-27 12:34 ` Zhen Lei
2023-05-31 0:17 ` Baoquan He
2023-05-31 0:17 ` Baoquan He
2023-05-31 2:19 ` Leizhen (ThunderTown)
2023-05-31 2:19 ` Leizhen (ThunderTown)
2023-05-31 7:41 ` Baoquan He
2023-05-31 7:41 ` Baoquan He
2023-05-31 8:26 ` Leizhen (ThunderTown)
2023-05-31 8:26 ` Leizhen (ThunderTown)
2023-05-27 12:34 ` [PATCH 3/6] kexec: clear crashk_res if all its memory has been released Zhen Lei
2023-05-27 12:34 ` Zhen Lei
2023-05-31 0:33 ` Baoquan He
2023-05-31 0:33 ` Baoquan He
2023-05-27 12:34 ` [PATCH 4/6] kexec: improve the readability of crash_shrink_memory() Zhen Lei
2023-05-27 12:34 ` Zhen Lei
2023-05-31 7:48 ` Baoquan He [this message]
2023-05-31 7:48 ` Baoquan He
2023-05-27 12:34 ` [PATCH 5/6] kexec: add helper __crash_shrink_memory() Zhen Lei
2023-05-27 12:34 ` Zhen Lei
2023-05-28 0:08 ` kernel test robot
2023-05-28 0:08 ` kernel test robot
2023-05-29 0:37 ` Leizhen (ThunderTown)
2023-05-29 0:37 ` Leizhen (ThunderTown)
2023-05-28 1:44 ` kernel test robot
2023-05-28 1:44 ` kernel test robot
2023-05-28 6:26 ` kernel test robot
2023-05-28 6:26 ` kernel test robot
2023-05-31 7:50 ` Baoquan He
2023-05-31 7:50 ` Baoquan He
2023-05-27 12:34 ` [PATCH 6/6] kexec: enable kexec_crash_size to support two crash kernel regions Zhen Lei
2023-05-27 12:34 ` Zhen Lei
2023-05-31 9:53 ` Baoquan He
2023-05-31 9:53 ` Baoquan He
2023-05-31 14:25 ` Leizhen (ThunderTown)
2023-05-31 14:25 ` Leizhen (ThunderTown)
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=ZHb7ubJYO2lyNkud@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder.leizhen@huawei.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 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.