Re: memblock vs early_res

[Yinghai Lu]

On 09/17/2010 01:47 PM, Jeremy Fitzhardinge wrote:
>  Hi Yinghai,
> 
> I have the patch below floating around in my tree to make sure that
> early-reserved highmem is honoured when freeing unreserved memory.  I
> was trying to rebase it to current linux-next and noticed that all the
> early_res stuff has been replaced with memblock.
> 
> Is this still an issue?  What would the memblock version of this patch
> look like?
> 

Not sure why this patch is needed.

For the early reserve ranges, that could be overlapped with high pages, is "KVA RAM",
but We do remove those range in active ranges array. [ in calculate_numa_remap_pages() ].
[
...
                memblock_x86_reserve_range(node_kva_final,
                              node_kva_final+(((u64)size)<<PAGE_SHIFT),
                              "KVA RAM");

                node_remap_start_pfn[nid] = node_kva_final>>PAGE_SHIFT;
                remove_active_range(nid, node_remap_start_pfn[nid],
                                         node_remap_start_pfn[nid] + size);
...
]

Can you check if Gianluca Guida still can duplicate the problem that will need his patch ?

Thanks

Yinghai Lu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/