Re: [PATCH 3/5] x86: Keep track of direct mapped pfn ranges

On Mon, Aug 13, 2012 at 04:47:02PM -0500, Jacob Shin wrote: > Update later calls to init_memory_mapping to keep track of direct mapped > pfn ranges so that at any point in time we can accurately represent what > memory ranges are direct mapped or not. Maybe we want to roll add_pfn_range_mapped() c

[PATCH 3/5] x86: Keep track of direct mapped pfn ranges

Update later calls to init_memory_mapping to keep track of direct mapped pfn ranges so that at any point in time we can accurately represent what memory ranges are direct mapped or not. Signed-off-by: Jacob Shin --- arch/x86/kernel/amd_gart_64.c |4 +++- arch/x86/mm/init_64.c |

Re: [PATCH 3/5] x86: Keep track of direct mapped pfn ranges

On Thu, Aug 09, 2012 at 04:23:07PM -0500, Jacob Shin wrote: > Update later calls to init_memory_mapping to keep track of direct mapped > pfn ranges. so that -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.o

[PATCH 3/5] x86: Keep track of direct mapped pfn ranges

Update later calls to init_memory_mapping to keep track of direct mapped pfn ranges. Signed-off-by: Jacob Shin --- arch/x86/kernel/amd_gart_64.c |4 +++- arch/x86/mm/init_64.c |3 +-- arch/x86/platform/efi/efi_64.c |2 ++ 3 files changed, 6 insertions(+), 3 deletions(-) di