|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v4 3/7] xen/arm: keep track of reserved-memory regions
Hi Stefano, On 06/08/2019 22:49, Stefano Stabellini wrote: As we parse the device tree in Xen, keep track of the reserved-memory regions as they need special treatment (follow-up patches will make use of the stored information.) Reuse process_memory_node to add reserved-memory regions to the bootinfo.reserved_mem array. Refuse to continue once we reach the max number of reserved memory regions to avoid accidentally mapping any portions of them into a VM. Signed-off-by: Stefano Stabellini <stefanos@xxxxxxxxxx> --- Changes in v4: - depth + 1 in process_reserved_memory_node Ah, you fixed it in this patch. But then, this does not match the documentation in patch #1. - pass address_cells and size_cells to device_tree_for_each_node - pass struct meminfo * instead of a boolean to process_memory_node - improve in-code comment I can't see any comment, is that an improvement? :) The cast is unnecessary.The rest of the code looks good. Pending the discussion about device_tree_for_each_node: Acked-by: Julien Grall <julien.grall@xxxxxxx> if ( address_cells < 1 || size_cells < 1 ) Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |