lkml.org 
[lkml]   [2012]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH V3 0/4] x86: Create direct mappings for E820_RAM only
Date
Currently kernel direct mappings are created for all pfns between
[ 0 to max_low_pfn ) and [ 4GB to max_pfn ). When we introduce memory
holes, we end up mapping memory ranges that are not backed by physical
DRAM. This is fine for lower memory addresses which can be marked as UC
by fixed/variable range MTRRs, however we run in to trouble with high
addresses.

The following patchset creates direct mappings only for E820_RAM regions
between 0 ~ max_low_pfn and 4GB ~ max_pfn. And leaves non-E820_RAM and
memory holes unmapped.

This third revision of the patchset attempts to resolve comments and
concerns from the following threads:

* https://lkml.org/lkml/2012/8/13/512
* https://lkml.org/lkml/2012/8/9/536
* https://lkml.org/lkml/2011/10/20/323

Jacob Shin (4):
x86: Move enabling of PSE and PGE out of init_memory_mapping
x86: find_early_table_space based on memory ranges that are being
mapped
x86: Only direct map addresses that are marked as E820_RAM
x86: Fixup code testing if a pfn is direct mapped

arch/x86/include/asm/page_types.h | 9 +++
arch/x86/kernel/cpu/amd.c | 6 +-
arch/x86/kernel/setup.c | 121 +++++++++++++++++++++++++++++++------
arch/x86/mm/init.c | 74 +++++++++++------------
arch/x86/mm/init_64.c | 6 +-
arch/x86/platform/efi/efi.c | 8 +--
6 files changed, 155 insertions(+), 69 deletions(-)

--
1.7.9.5




\
 
 \ /
  Last update: 2012-08-15 01:22    [W:0.181 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site