On Wed, Dec 14, 2016 at 4:21 PM, Laura Abbott <labbott@xxxxxxxxxx> wrote: > On 12/14/2016 12:45 PM, Rob Herring wrote: >> On Wed, Nov 23, 2016 at 5:37 AM, Jason Liu <jason.hui.liu@xxxxxxx> wrote: >>> Need ensure the cma reserved region not cross the low/high memory boundary >>> when using the dynamic allocation methond through device-tree, otherwise, >>> kernel will fail to boot up when cma reserved region cross how/high mem. >> >> The kernel command line code setting CMA already deals with this. Why >> don't we just call the CMA code (cma_declare_contiguous) to deal with >> this? >> >> Rob >> > > That was proposed in the first version[1] but I think this is a generic > problem not specific to CMA. Even non-CMA reservations trying to span > zones could cause problems so the devicetree allocation code should > restrict reservations to a single zone. Fair enough, but that's not what this patch does. It's only for CMA. Rob -- 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
