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? I can see it for e.g. framebuffer or cma which the OS might actually use under special circumstances and therefore need more info than just "don't use this". It looks like as well as observing the requested reservations Xen might also need to somehow reflect them to dom0, I need to think on this. If there are any useful references over and above Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt then I'd be glad to see them. Ian. -- 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
