提交 0f96ae29 编写于 作者: S Shailendra Verma 提交者: Linus Torvalds
上级 f0d6647e
...@@ -182,7 +182,7 @@ int __init cma_init_reserved_mem(phys_addr_t base, phys_addr_t size, ...@@ -182,7 +182,7 @@ int __init cma_init_reserved_mem(phys_addr_t base, phys_addr_t size,
if (!size || !memblock_is_region_reserved(base, size)) if (!size || !memblock_is_region_reserved(base, size))
return -EINVAL; return -EINVAL;
/* ensure minimal alignment requied by mm core */ /* ensure minimal alignment required by mm core */
alignment = PAGE_SIZE << max(MAX_ORDER - 1, pageblock_order); alignment = PAGE_SIZE << max(MAX_ORDER - 1, pageblock_order);
/* alignment should be aligned with order_per_bit */ /* alignment should be aligned with order_per_bit */
...@@ -238,7 +238,7 @@ int __init cma_declare_contiguous(phys_addr_t base, ...@@ -238,7 +238,7 @@ int __init cma_declare_contiguous(phys_addr_t base,
/* /*
* high_memory isn't direct mapped memory so retrieving its physical * high_memory isn't direct mapped memory so retrieving its physical
* address isn't appropriate. But it would be useful to check the * address isn't appropriate. But it would be useful to check the
* physical address of the highmem boundary so it's justfiable to get * physical address of the highmem boundary so it's justifiable to get
* the physical address from it. On x86 there is a validation check for * the physical address from it. On x86 there is a validation check for
* this case, so the following workaround is needed to avoid it. * this case, so the following workaround is needed to avoid it.
*/ */
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册