From: Matthias Brugger <matthias.bgg@gmail.com>
To: Bhupesh Sharma <bhsharma@redhat.com>,
linux-arm-kernel@lists.infradead.org
Cc: will.deacon@arm.com, linux-kernel@vger.kernel.org,
takahiro.akashi@linaro.org, james.morse@arm.com,
bhupesh.linux@gmail.com
Subject: Re: [PATCH] arm64/kexec: Use consistent convention of initializing 'kxec_buf.mem' with KEXEC_BUF_MEM_UNKNOWN
Date: Thu, 11 Jul 2019 16:52:10 +0200 [thread overview]
Message-ID: <17b63547-0f03-baaf-775c-2da75aa40ee3@gmail.com> (raw)
In-Reply-To: <1562846252-7441-1-git-send-email-bhsharma@redhat.com>
On 11/07/2019 13:57, Bhupesh Sharma wrote:
> With commit b6664ba42f14 ("s390, kexec_file: drop arch_kexec_mem_walk()"),
> we introduced the KEXEC_BUF_MEM_UNKNOWN macro. If kexec_buf.mem is set
> to this value, kexec_locate_mem_hole() will try to allocate free memory.
>
> While other arch(s) like s390 and x86_64 already use this macro to
> initialize kexec_buf.mem with, arm64 uses an equivalent value of 0.
> Replace it with KEXEC_BUF_MEM_UNKNOWN, to keep the convention of
> initializing 'kxec_buf.mem' consistent across various archs.
>
> Cc: takahiro.akashi@linaro.org
> Cc: james.morse@arm.com
> Cc: will.deacon@arm.com
> Cc: linux-arm-kernel@lists.infradead.org
> Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
> ---
Reviewed-by: Matthias Brugger <mbrugger@suse.com>
> arch/arm64/kernel/kexec_image.c | 2 +-
> arch/arm64/kernel/machine_kexec_file.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/kernel/kexec_image.c b/arch/arm64/kernel/kexec_image.c
> index 2514fd6f12cb..29a9428486a5 100644
> --- a/arch/arm64/kernel/kexec_image.c
> +++ b/arch/arm64/kernel/kexec_image.c
> @@ -84,7 +84,7 @@ static void *image_load(struct kimage *image,
>
> kbuf.buffer = kernel;
> kbuf.bufsz = kernel_len;
> - kbuf.mem = 0;
> + kbuf.mem = KEXEC_BUF_MEM_UNKNOWN;
> kbuf.memsz = le64_to_cpu(h->image_size);
> text_offset = le64_to_cpu(h->text_offset);
> kbuf.buf_align = MIN_KIMG_ALIGN;
> diff --git a/arch/arm64/kernel/machine_kexec_file.c b/arch/arm64/kernel/machine_kexec_file.c
> index 58871333737a..ba78ee7ca990 100644
> --- a/arch/arm64/kernel/machine_kexec_file.c
> +++ b/arch/arm64/kernel/machine_kexec_file.c
> @@ -177,7 +177,7 @@ int load_other_segments(struct kimage *image,
> if (initrd) {
> kbuf.buffer = initrd;
> kbuf.bufsz = initrd_len;
> - kbuf.mem = 0;
> + kbuf.mem = KEXEC_BUF_MEM_UNKNOWN;
> kbuf.memsz = initrd_len;
> kbuf.buf_align = 0;
> /* within 1GB-aligned window of up to 32GB in size */
> @@ -204,7 +204,7 @@ int load_other_segments(struct kimage *image,
> dtb_len = fdt_totalsize(dtb);
> kbuf.buffer = dtb;
> kbuf.bufsz = dtb_len;
> - kbuf.mem = 0;
> + kbuf.mem = KEXEC_BUF_MEM_UNKNOWN;
> kbuf.memsz = dtb_len;
> /* not across 2MB boundary */
> kbuf.buf_align = SZ_2M;
>
next prev parent reply other threads:[~2019-07-11 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 11:57 Bhupesh Sharma
2019-07-11 14:52 ` Matthias Brugger [this message]
2019-07-26 16:49 ` James Morse
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=17b63547-0f03-baaf-775c-2da75aa40ee3@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=bhsharma@redhat.com \
--cc=bhupesh.linux@gmail.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®