On 2014-02-10 22:59, Grant Likely wrote:
On Thu, 06 Feb 2014 14:26:13 +0100, Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> wrote: > Hello, > > On 2014-02-05 11:15, Grant Likely wrote: > > On Tue, 04 Feb 2014 13:09:32 +0100, Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> wrote: > > > Enable reserved memory initialization from device tree. > > > > > > Cc: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx> > > > Cc: Laura Abbott <lauraa@xxxxxxxxxxxxxx> > > > Signed-off-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> > > > --- > > > arch/arm/mm/init.c | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > > > diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c > > > index 804d61566a53..ebafdb479410 100644 > > > --- a/arch/arm/mm/init.c > > > +++ b/arch/arm/mm/init.c > > > @@ -17,6 +17,7 @@ > > > #include <linux/nodemask.h> > > > #include <linux/initrd.h> > > > #include <linux/of_fdt.h> > > > +#include <linux/of_reserved_mem.h> > > > #include <linux/highmem.h> > > > #include <linux/gfp.h> > > > #include <linux/memblock.h> > > > @@ -323,6 +324,8 @@ void __init arm_memblock_init(struct meminfo *mi, > > > if (mdesc->reserve) > > > mdesc->reserve(); > > > > > > + early_init_dt_scan_reserved_mem(); > > > + > > > > The new binding is being made fundamental. If the reserved-memory node > > is present, then it needs to be honored, even if the kernel doesn't know > > how to use the regions. Therefore, This needs to be unconditional for > > all architectures. The hook should be called in early_init_dt_scan() > > (drivers/of/fdt.c) immediately after the early_init_dt_scan_memory() > > hook. > > In theory this will be the best solution, but it practice there is a > problem. early_init_dt_scan() is called as the first function from kernel > booting code. That time there is no memory yet added to the system, so it > would be really hard to reserve anything. Memory nodes are being added > later either with memblock_add() or by some other arch specific way. Hmmm, depends on the architecture. On ARM the memory is loaded into the meminfo structure first, and it isn't until arm_memblock_init() that memblock_add() gets called on all the regions. Some architectures do the memblock_add() directly from early_init_dt_add_memory_arch() function. The default early_init_dt_add_memory_arch() in drivers/of/fdt.c is overridden by ARM and a number of other architectures. However... > Finally, once all memory has been added to the system we can parse and > reserve all regions defined in the device tree. This really requires > creating another function which will be called by arch specific code. ...Or it means getting rid of meminfo entirely so that memblock is available earlier. Laura Abbott has just posted v2 of her series to do exactly that. If you base on that then you should be able to do exactly what I suggested.
I've checked Laura's patches and in fact it is possible to do memory reservation as a last step in early_init_dt_scan_memory(). However still see some problem which I have no idea how to resolve. Right now I focus only on ARM, so I have no idea how it is solved by other architectures. On of the key features of the new binding is the ability to automatically allocate reserved regions of the given size. However kernel, initrd, dt and other sub-arch specific critical regions are marked/allocated in arm_memblock_init(), which is called after setup_machine_fdt(). This might lead to some serious failures when automatically reserved region overlaps with some critical resources. Do you have any idea how to solve this without a new callback? Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland -- 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
