From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 03/14] powerpc, kexec_file: factor out memblock-based arch_kexec_walk_mem()
Date: Mon, 9 Jul 2018 14:49:54 +0900 [thread overview]
Message-ID: <20180709054953.GR28220@linaro.org> (raw)
In-Reply-To: <8a59db79-6379-550b-b20e-01036626904e@arm.com>
James,
On Tue, Jul 03, 2018 at 05:36:24PM +0100, James Morse wrote:
> Hi Akashi,
>
> On 23/06/18 03:20, AKASHI Takahiro wrote:
> > Memblock list is another source for usable system memory layout.
> > A merged new arch_kexec_walk_mem() will walk through either io resource
> > list or memblock list depending on CONFIG_ARCH_DISCARD_MEMBLOCK so that
> > arm64, in addition to powerpc, will be able to utilize this generic
> > function for kexec_file.
>
> > diff --git a/arch/powerpc/kernel/machine_kexec_file_64.c b/arch/powerpc/kernel/machine_kexec_file_64.c
> > index 0bd23dc789a4..3d4be91786ce 100644
> > --- a/arch/powerpc/kernel/machine_kexec_file_64.c
> > +++ b/arch/powerpc/kernel/machine_kexec_file_64.c
>
> Does this file still need its memblock.h include?
OK. Will remove it.
>
> > diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c
> > index 63c7ce1c0c3e..563acd1c9a61 100644
> > --- a/kernel/kexec_file.c
> > +++ b/kernel/kexec_file.c
> > @@ -16,6 +16,7 @@
> > #include <linux/file.h>
> > #include <linux/slab.h>
> > #include <linux/kexec.h>
> > +#include <linux/memblock.h>
> > #include <linux/mutex.h>
> > #include <linux/list.h>
> > #include <linux/fs.h>
> > @@ -501,6 +502,53 @@ static int locate_mem_hole_callback(struct resource *res, void *arg)
> > return locate_mem_hole_bottom_up(start, end, kbuf);
> > }
> >
> > +#if defined(CONFIG_HAVE_MEMBLOCK) && !defined(CONFIG_ARCH_DISCARD_MEMBLOCK)
>
> The only caller is also guarded by these same ifdefs. Can't we remove this and
> rely on the compilers dead-code elimination to remove this function when its not
> needed?
I don't think we can remove this #ifdef.
"for_each_free_mem_range[_reverse]()" is defined under CONFIG_HAVE_MEMBLOCK
in memblock.h. If some architecture wants to support KEXEC_FILE but
doesn't have HAVE_MEMBLOCK, compiling kexec_file.c will fail.
>
> > +static int kexec_walk_memblock(struct kexec_buf *kbuf,
> > + int (*func)(struct resource *, void *))
> > +{
> > + u64 i;
> > + phys_addr_t mstart, mend;
> > + struct resource res = { };
> > + int ret = 0;
>
>
> Keeping this patch as 'just' moving code would avoid having to play
> spot-the-difference:
OK. I will split this patch into two.
But just "moving" is impossible because the function names will be
duplicated in kexec_file.c.
> > + if (kbuf->image->type == KEXEC_TYPE_CRASH)
> > + return func(&crashk_res, kbuf);
>
> This will be new for powerpc, but any attempt to use it should be caught by
> arch_kexec_kernel_image_probe(), which has:
> | /* We don't support crash kernels yet. */
> | if (image->type == KEXEC_TYPE_CRASH)
> | return -EOPNOTSUPP;
>
>
> Looks good to me! For what its worth:
> Acked-by: James Morse <james.morse@arm.com>
Thank you for your reviews.
-Takahiro AKASHI
>
> Thanks,
>
> James
next prev parent reply other threads:[~2018-07-09 5:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 2:20 [PATCH v10 00/14] arm64: kexec: add kexec_file_load() support AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 01/14] asm-generic: add kexec_file_load system call to unistd.h AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 02/14] kexec_file: make kexec_image_post_load_cleanup_default() global AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 03/14] powerpc, kexec_file: factor out memblock-based arch_kexec_walk_mem() AKASHI Takahiro
2018-07-03 16:36 ` James Morse
2018-07-09 5:49 ` AKASHI Takahiro [this message]
2018-07-09 11:03 ` James Morse
2018-06-23 2:20 ` [PATCH v10 04/14] of/fdt: add helper functions for handling properties AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 05/14] arm64: add image head flag definitions AKASHI Takahiro
2018-07-03 16:34 ` James Morse
2018-06-23 2:20 ` [PATCH v10 06/14] arm64: cpufeature: add MMFR0 helper functions AKASHI Takahiro
2018-07-03 16:33 ` James Morse
2018-06-23 2:20 ` [PATCH v10 07/14] arm64: enable KEXEC_FILE config AKASHI Takahiro
2018-07-03 16:33 ` James Morse
2018-07-09 6:31 ` AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 08/14] arm64: kexec_file: load initrd and device-tree AKASHI Takahiro
2018-07-03 16:32 ` James Morse
2018-07-10 7:37 ` AKASHI Takahiro
2018-07-10 15:25 ` James Morse
2018-07-11 2:49 ` AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 09/14] arm64: kexec_file: allow for loading Image-format kernel AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 10/14] arm64: kexec_file: add crash dump support AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 11/14] arm64: kexec_file: invoke the kernel without purgatory AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 12/14] include: pe.h: remove message[] from mz header definition AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 13/14] arm64: kexec_file: add kernel signature verification support AKASHI Takahiro
2018-07-03 17:47 ` James Morse
2018-07-09 9:01 ` AKASHI Takahiro
2018-06-23 2:20 ` [PATCH v10 14/14] arm64: kexec_file: add kaslr support AKASHI Takahiro
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=20180709054953.GR28220@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=linux-arm-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).