From: Jan Kiszka <jan.kiszka@web.de>
To: Frank Rowand <frowand.list@gmail.com>, Rob Herring <robh+dt@kernel.org>
Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Pantelis Antoniou <panto@antoniou-consulting.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Jailhouse <jailhouse-dev@googlegroups.com>
Subject: Re: [PATCH v7 2/5] of: change overlay apply input data from unflattened to FDT
Date: Thu, 5 Apr 2018 21:17:25 +0200 [thread overview]
Message-ID: <48bb616d-000f-834c-fcfd-c5441a6b61d8@web.de> (raw)
In-Reply-To: <de44758c-6c40-b951-e235-b2307ae6257e@gmail.com>
On 2018-04-05 21:13, Frank Rowand wrote:
> On 04/04/18 17:55, Rob Herring wrote:
>> On Wed, Apr 4, 2018 at 5:35 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
>>> Hi Frank,
>>>
>>> On 2018-03-04 01:17, frowand.list@gmail.com wrote:
>>>> From: Frank Rowand <frank.rowand@sony.com>
>>>>
>>>> Move duplicating and unflattening of an overlay flattened devicetree
>>>> (FDT) into the overlay application code. To accomplish this,
>>>> of_overlay_apply() is replaced by of_overlay_fdt_apply().
>>>>
>>>> The copy of the FDT (aka "duplicate FDT") now belongs to devicetree
>>>> code, which is thus responsible for freeing the duplicate FDT. The
>>>> caller of of_overlay_fdt_apply() remains responsible for freeing the
>>>> original FDT.
>>>>
>>>> The unflattened devicetree now belongs to devicetree code, which is
>>>> thus responsible for freeing the unflattened devicetree.
>>>>
>>>> These ownership changes prevent early freeing of the duplicated FDT
>>>> or the unflattened devicetree, which could result in use after free
>>>> errors.
>>>>
>>>> of_overlay_fdt_apply() is a private function for the anticipated
>>>> overlay loader.
>>>
>>> We are using of_fdt_unflatten_tree + of_overlay_apply in the
>>> (out-of-tree) Jailhouse loader driver in order to register a virtual
>>> device during hypervisor activation with Linux. The DT overlay is
>>> created from a a template but modified prior to application to account
>>> for runtime-specific parameters. See [1] for the current implementation.
>>>
>>> I'm now wondering how to model that scenario best with the new API.
>>> Given that the loader lost ownership of the unflattened tree but the
>>> modification API exist only for the that DT state, I'm not yet seeing a
>>> clear solution. Should we apply the template in disabled form (status =
>>> "disabled"), modify it, and then activate it while it is already applied?
>>
>> No. I don't think that will work.
>
> I don't think it will work either. The drivers won't be probed if the
> nodes are disabled.
>
That would be the purpose of registering it disabled. The question is:
Would it be probed at the point when we enabled it while being applied?
If not, strike this.
Jan
next prev parent reply other threads:[~2018-04-05 19:17 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 0:17 [PATCH v7 0/5] of: change overlay apply input data from unflattened frowand.list
2018-03-04 0:17 ` [PATCH v7 1/5] x86: devicetree: fix config option around x86_flattree_get_config() frowand.list
2018-03-04 0:27 ` Frank Rowand
2018-03-04 7:20 ` Thomas Gleixner
2018-03-04 0:17 ` [PATCH v7 2/5] of: change overlay apply input data from unflattened to FDT frowand.list
2018-04-04 22:35 ` Jan Kiszka
2018-04-05 0:55 ` Rob Herring
2018-04-05 7:22 ` Jan Kiszka
2018-04-05 19:16 ` Frank Rowand
2018-04-05 19:26 ` Rob Herring
2018-04-05 19:37 ` Frank Rowand
2018-04-05 19:13 ` Frank Rowand
2018-04-05 19:17 ` Jan Kiszka [this message]
2018-04-05 18:59 ` Frank Rowand
2018-04-05 19:13 ` Jan Kiszka
2018-04-05 19:28 ` Frank Rowand
2018-04-05 19:38 ` Jan Kiszka
2018-04-05 20:33 ` Frank Rowand
2018-04-05 21:12 ` Rob Herring
2018-04-11 5:42 ` Jan Kiszka
2018-04-22 10:30 ` Jan Kiszka
2018-04-23 22:38 ` Frank Rowand
2018-04-24 5:29 ` Jan Kiszka
2018-04-24 16:08 ` Alan Tull
2018-04-24 18:26 ` Alan Tull
2018-04-25 5:38 ` Jan Kiszka
2018-04-24 21:15 ` Frank Rowand
2018-04-25 5:22 ` Jan Kiszka
2018-04-25 18:56 ` Frank Rowand
2018-04-25 19:02 ` Frank Rowand
2018-04-25 19:40 ` Jan Kiszka
2018-04-25 19:53 ` Geert Uytterhoeven
2018-04-25 20:09 ` Jan Kiszka
2018-04-25 23:07 ` Frank Rowand
2018-04-24 20:56 ` Frank Rowand
2018-04-25 5:23 ` Jan Kiszka
2018-04-25 18:40 ` Frank Rowand
2018-04-25 20:07 ` Jan Kiszka
2018-04-25 20:26 ` Alan Tull
2018-04-26 0:20 ` Frank Rowand
2018-04-25 14:59 ` Alan Tull
2018-04-25 17:41 ` Frank Rowand
2018-04-25 18:19 ` Alan Tull
2018-04-26 0:07 ` Frank Rowand
2018-04-26 0:10 ` Frank Rowand
2018-03-04 0:17 ` [PATCH v7 3/5] of: Documentation: of_overlay_apply() replaced by of_overlay_fdt_apply() frowand.list
2018-03-04 0:17 ` [PATCH v7 4/5] of: convert unittest overlay devicetree source to sugar syntax frowand.list
2018-03-04 0:17 ` [PATCH v7 5/5] of: improve reporting invalid overlay target path frowand.list
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=48bb616d-000f-834c-fcfd-c5441a6b61d8@web.de \
--to=jan.kiszka@web.de \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert@linux-m68k.org \
--cc=jailhouse-dev@googlegroups.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=panto@antoniou-consulting.com \
--cc=robh+dt@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).