From: geoff.levand@linaro.org (Geoff Levand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5.5] of/fdt: export fdt blob as /sys/firmware/fdt
Date: Wed, 19 Nov 2014 10:32:51 -0800 [thread overview]
Message-ID: <1416421971.23886.71.camel@smoke> (raw)
In-Reply-To: <1416402576.29243.35.camel@citrix.com>
Hi Ian,
On Wed, 2014-11-19 at 13:09 +0000, Ian Campbell wrote:
> On Tue, 2014-11-18 at 22:11 +0000, Grant Likely wrote:
> > > > * It also helps with exposing the reserved map to userspace, but kexec
> > > > has done without that feature for years, and it is in the process of
> > > > being deprecated in favour of /reserved-memory anyway.
> > >
> > > This is the first I'd heard of the reserve map being deprecated, and
> > > we're going to have DTs with reserved map entries for a long time going
> > > forwards.
> >
> > Deprecated, not removed or disabled. It will still work pretty much
> > forever, but users should be encouraged to move to the reserve-memory
> > tree.
>
> I'm curious why that should be for the "OS should never touch this, here
> be dragons" type memory, what are the benefits of the new scheme in that
> case?
/memreserve/ device tree entries are not available in /proc/device-tree,
but reserved-memory nodes are. Some solution is needed to get all
reserved memory info into the dtb passed to the second stage kernel
during a kexec re-boot.
-Geoff
WARNING: multiple messages have this Message-ID (diff)
From: Geoff Levand <geoff.levand-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Ian Campbell <Ian.Campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Cc: Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v5.5] of/fdt: export fdt blob as /sys/firmware/fdt
Date: Wed, 19 Nov 2014 10:32:51 -0800 [thread overview]
Message-ID: <1416421971.23886.71.camel@smoke> (raw)
In-Reply-To: <1416402576.29243.35.camel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Hi Ian,
On Wed, 2014-11-19 at 13:09 +0000, Ian Campbell wrote:
> On Tue, 2014-11-18 at 22:11 +0000, Grant Likely wrote:
> > > > * It also helps with exposing the reserved map to userspace, but kexec
> > > > has done without that feature for years, and it is in the process of
> > > > being deprecated in favour of /reserved-memory anyway.
> > >
> > > This is the first I'd heard of the reserve map being deprecated, and
> > > we're going to have DTs with reserved map entries for a long time going
> > > forwards.
> >
> > Deprecated, not removed or disabled. It will still work pretty much
> > forever, but users should be encouraged to move to the reserve-memory
> > tree.
>
> I'm curious why that should be for the "OS should never touch this, here
> be dragons" type memory, what are the benefits of the new scheme in that
> case?
/memreserve/ device tree entries are not available in /proc/device-tree,
but reserved-memory nodes are. Some solution is needed to get all
reserved memory info into the dtb passed to the second stage kernel
during a kexec re-boot.
-Geoff
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-19 18:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 17:05 [PATCH v5.5] of/fdt: export fdt blob as /sys/firmware/fdt Ard Biesheuvel
2014-11-14 17:05 ` Ard Biesheuvel
2014-11-18 16:51 ` Grant Likely
2014-11-18 16:51 ` Grant Likely
2014-11-18 17:25 ` Mark Rutland
2014-11-18 17:25 ` Mark Rutland
2014-11-18 22:11 ` Grant Likely
2014-11-18 22:11 ` Grant Likely
2014-11-18 23:11 ` Rob Herring
2014-11-18 23:11 ` Rob Herring
2014-11-19 8:24 ` Ard Biesheuvel
2014-11-19 8:24 ` Ard Biesheuvel
2014-11-19 15:10 ` Grant Likely
2014-11-19 15:10 ` Grant Likely
2014-11-19 13:09 ` Ian Campbell
2014-11-19 13:09 ` Ian Campbell
2014-11-19 15:07 ` Grant Likely
2014-11-19 15:07 ` Grant Likely
2014-11-19 18:32 ` Geoff Levand [this message]
2014-11-19 18:32 ` Geoff Levand
2014-11-21 14:58 ` Grant Likely
2014-11-21 14:58 ` Grant Likely
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=1416421971.23886.71.camel@smoke \
--to=geoff.levand@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.