From: Mitchel Humpherys <mitchelh@codeaurora.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] of: Check for overlap in reserved memory regions
Date: Fri, 04 Dec 2015 09:27:50 -0800 [thread overview]
Message-ID: <vnkwy4daktt5.fsf@codeaurora.org> (raw)
In-Reply-To: <1447294799.29472.15.camel@ellerman.id.au> (Michael Ellerman's message of "Thu, 12 Nov 2015 13:19:59 +1100")
On Thu, Nov 12 2015 at 01:19:59 PM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> On Tue, 2015-09-15 at 18:30 -0700, Mitchel Humpherys wrote:
>
>> Any overlap in the reserved memory regions (those specified in the
>> reserved-memory DT node) is a bug.
>
> Can you expand a bit on why you think it's a bug? I assume it was discussed at
> some point on the list but I didn't see it sorry.
The reason I think it's a bug is because the overlapping memory could be
handed out to multiple firmwares, which generally ends in "random"
firmware crashes. We've found by sad experience that root-causing such
a crash can be quite difficult.
Is there a valid use case for overlapping regions? I can't think of
one...
> There's nothing I can see in the binding document[1] about whether regions can
> overlap, or what it would mean if they did.
You're right, the bindings document doesn't say anything about
overlapping memory regions. I can submit something unless someone comes
up with a reason why we should allow overlapping memory regions.
> If we want to declare that overlapping regions are always a bug then there
> should be some text in the binding explaining that. There's also the
> possibility that we have existing device trees in the wild that contain
> overlapping regions, and whether we think it's OK to retrospectively declare
> that they're incorrect.
I did a quick survey of in-tree users of reserved-memory and couldn't
find any overlapping regions.
-Mitch
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-12-04 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 1:30 [PATCH v2] of: Check for overlap in reserved memory regions Mitchel Humpherys
2015-10-13 20:13 ` Rob Herring
2015-11-12 2:19 ` Michael Ellerman
2015-12-04 17:27 ` Mitchel Humpherys [this message]
[not found] ` <1442367036-15205-1-git-send-email-mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-11-10 4:29 ` Michael Ellerman
2015-11-10 4:41 ` Rob Herring
2015-11-10 4:57 ` Michael Ellerman
2015-11-12 8:06 ` Michael Ellerman
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=vnkwy4daktt5.fsf@codeaurora.org \
--to=mitchelh@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mpe@ellerman.id.au \
--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).