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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
