From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Youlin Song <syl.loop@gmail.com>,
"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"paulus@samba.org" <paulus@samba.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc/prom: move the device tree to the right space
Date: Wed, 7 Sep 2022 17:11:08 +0000 [thread overview]
Message-ID: <03df3312-cd60-554d-9711-9b87d43dfe7e@csgroup.eu> (raw)
In-Reply-To: <20210303050054.3343-1-syl.loop@gmail.com>
Le 03/03/2021 à 06:00, Youlin Song a écrit :
> If the device tree has been allocated memory and it will
> be in the memblock reserved space.Obviously it is in a
> valid memory declaration and will be mapped by the kernel.
Could you please provide clearer explanation ? I don't understand what
you are doing and why.
Especially, the Subject says you move the device tree, but I can't see
any move in your patch, only some change in the 'if'.
Thanks
Christophe
>
> Signed-off-by: Youlin Song <syl.loop@gmail.com>
> ---
> arch/powerpc/kernel/prom.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/kernel/prom.c b/arch/powerpc/kernel/prom.c
> index 9a4797d1d40d..ef5f93e7d7f2 100644
> --- a/arch/powerpc/kernel/prom.c
> +++ b/arch/powerpc/kernel/prom.c
> @@ -121,7 +121,7 @@ static void __init move_device_tree(void)
> size = fdt_totalsize(initial_boot_params);
>
> if ((memory_limit && (start + size) > PHYSICAL_START + memory_limit) ||
> - !memblock_is_memory(start + size - 1) ||
> + (!memblock_is_memory(start + size - 1) && !memblock_is_reserved(start + size - 1)) ||
> overlaps_crashkernel(start, size) || overlaps_initrd(start, size)) {
> p = memblock_alloc_raw(size, PAGE_SIZE);
> if (!p)
prev parent reply other threads:[~2022-09-07 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 5:00 [PATCH] powerpc/prom: move the device tree to the right space Youlin Song
2022-09-07 17:11 ` Christophe Leroy [this message]
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=03df3312-cd60-554d-9711-9b87d43dfe7e@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=syl.loop@gmail.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;
as well as URLs for NNTP newsgroup(s).