From: Vincent Whitchurch <vincent.whitchurch@axis.com>
To: Rob Herring <robh@kernel.org>
Cc: "jdike@addtoit.com" <jdike@addtoit.com>,
"richard@nod.at" <richard@nod.at>,
"anton.ivanov@cambridgegreys.com"
<anton.ivanov@cambridgegreys.com>, kernel <kernel@axis.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-um@lists.infradead.org" <linux-um@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] um: Add devicetree support
Date: Tue, 18 Jan 2022 15:20:13 +0100 [thread overview]
Message-ID: <20220118142013.GA556@axis.com> (raw)
In-Reply-To: <YeF/Vbxo6fAt0WLp@robh.at.kernel.org>
On Fri, Jan 14, 2022 at 02:49:09PM +0100, Rob Herring wrote:
> On Wed, Dec 08, 2021 at 04:11:23PM +0100, Vincent Whitchurch wrote:
> > --- /dev/null
> > +++ b/arch/um/kernel/dtb.c
> > @@ -0,0 +1,41 @@
> > +// SPDX-License-Identifier: GPL-2.0-only
> > +
> > +#include <linux/init.h>
> > +#include <linux/of_fdt.h>
> > +#include <linux/printk.h>
> > +#include <linux/memblock.h>
> > +#include <init.h>
> > +
> > +#include "um_arch.h"
> > +
> > +static char *dtb __initdata;
> > +
> > +void uml_dtb_init(void)
> > +{
> > + long long size;
> > + void *area;
> > +
> > + area = uml_load_file(dtb, &size);
> > + if (!area)
> > + return;
> > +
> > + if (!early_init_dt_scan(area)) {
> > + pr_err("invalid DTB %s\n", dtb);
> > + memblock_free(area, size);
> > + return;
> > + }
> > +
> > + unflatten_device_tree();
> > + early_init_fdt_scan_reserved_mem();
>
> These should be reversed. early_init_fdt_scan_reserved_mem() works on
> the flat tree. Reserved memory needs to be reserved before
> unflatten_device_tree() starts allocating memory. Though I imagine that
> doesn't really matter for UML.
I only tested dynamic allocation of reserved memory, and that,
unsuprisingly, works regardless of the order. But I'll send a patch to
change it.
> Also, does the dtb end up in permanently allocated memory (i.e. not
> init)? It needs to be if not.
The dtb is allocated with memblock_alloc() in arch/um/kernel/load_file.c
and is never freed (except on an error from early_init_dt_scan() as in
the above hunk), so I think this is already taken care of.
next prev parent reply other threads:[~2022-01-18 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 15:11 [PATCH 0/2] Devicetree support for UML Vincent Whitchurch
2021-12-08 15:11 ` [PATCH 1/2] um: Extract load file helper from initrd.c Vincent Whitchurch
2021-12-08 15:11 ` [PATCH 2/2] um: Add devicetree support Vincent Whitchurch
2022-01-14 13:49 ` Rob Herring
2022-01-18 14:20 ` Vincent Whitchurch [this message]
2021-12-21 20:55 ` [PATCH 0/2] Devicetree support for UML Richard Weinberger
2021-12-21 20:56 ` Johannes Berg
2021-12-21 21:13 ` Richard Weinberger
2021-12-22 10:23 ` Vincent Whitchurch
2021-12-22 19:31 ` Richard Weinberger
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=20220118142013.GA556@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=devicetree@vger.kernel.org \
--cc=jdike@addtoit.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=robh@kernel.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).