[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQUNwK5=Nos7Ce_DS1aSXgf0WNUgE=5HXnt4E01JWYbWjQ@mail.gmail.com>
Date: Fri, 16 Dec 2011 12:59:38 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Jacob Shin <jacob.shin@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"Herrmann3, Andreas" <Andreas.Herrmann3@....com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Joerg Roedel <joerg.roedel@....com>
Subject: Re: [PATCH 1/1] x86: Exclude E820_RESERVED regions and memory holes
above 4 GB from direct mapping.
On Fri, Dec 16, 2011 at 10:32 AM, H. Peter Anvin <hpa@...or.com> wrote:
>
> Well, there are two options for memory hotplug: either we always leave
> address space that can be used for memory hotplug mapped at all times, or we
> need to track it anyway. Either way we need to know where there regions
> are. Am I correct that right now we always map memory hotpluggable regions,
> being below the top pfn?
in arch/x86/mm/init_64.c::arch_add_memory()
it will call init_memory_mapping to map new added memory.
and will update max_pfn_mapped, max-pfn, max_low_pfn.
Thanks
Yinghai Lu
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists