From: Tang Chen <tangchen@cn.fujitsu.com>
To: mingo@redhat.com, hpa@zytor.com, yinghai@kernel.org,
penberg@kernel.org, jacob.shin@amd.com, tglx@linutronix.de,
lenb@kernel.org, rjw@sisk.pl
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, x86@kernel.org
Subject: [PATCH RESEND 2/3] x86, mm: Update min_pfn_mapped in add_pfn_range_mapped().
Date: Mon, 2 Sep 2013 18:30:28 +0800 [thread overview]
Message-ID: <1378117829-9095-3-git-send-email-tangchen@cn.fujitsu.com> (raw)
In-Reply-To: <1378117829-9095-1-git-send-email-tangchen@cn.fujitsu.com>
In current kernel, we update min_pfn_mapped and max_pfn_mapped like this:
init_mem_mapping()
{
while ( a loop iterates all memory ranges ) {
init_range_memory_mapping();
|->init_memory_mapping()
|->kernel_physical_mapping_init()
|->add_pfn_range_mapped()
|-> update max_pfn_mapped;
update min_pfn_mapped;
}
}
max_pfn_mapped is updated in add_pfn_range_mapped() when a range of memory
is mapped. But min_pfn_mapped is updated in init_mem_mapping(). We can also
update min_pfn_mapped in add_pfn_range_mapped().
Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
---
arch/x86/mm/init.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 5b2eaca..a97749f 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@ -313,6 +313,7 @@ static void add_pfn_range_mapped(unsigned long start_pfn, unsigned long end_pfn)
nr_pfn_mapped = clean_sort_range(pfn_mapped, E820_X_MAX);
max_pfn_mapped = max(max_pfn_mapped, end_pfn);
+ min_pfn_mapped = min(min_pfn_mapped, start_pfn);
}
bool pfn_range_is_mapped(unsigned long start_pfn, unsigned long end_pfn)
@@ -442,7 +443,6 @@ void __init init_mem_mapping(void)
new_mapped_ram_size = init_range_memory_mapping(start,
last_start);
last_start = start;
- min_pfn_mapped = last_start >> PAGE_SHIFT;
/* only increase step_size after big range get mapped */
if (new_mapped_ram_size > mapped_ram_size)
step_size <<= STEP_SIZE_SHIFT;
--
1.7.1
next prev parent reply other threads:[~2013-09-02 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 10:30 [PATCH RESEND 0/3] x86, ACPI, mm: Cleanup for {max|low|max_low}_pfn_mapped Tang Chen
2013-09-02 10:30 ` [PATCH RESEND 1/3] x86, ACPI, mm: Kill max_low_pfn_mapped Tang Chen
2013-09-02 10:30 ` Tang Chen [this message]
2013-09-02 18:41 ` [PATCH RESEND 2/3] x86, mm: Update min_pfn_mapped in add_pfn_range_mapped() Yinghai Lu
2013-09-03 1:06 ` Tang Chen
2013-09-03 2:48 ` Yinghai Lu
2013-09-03 5:38 ` Tang Chen
2013-09-03 6:34 ` Yinghai Lu
2013-09-02 10:30 ` [PATCH RESEND 3/3] x86, mm: Move max_pfn_mapped definition to init.c Tang Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1378117829-9095-3-git-send-email-tangchen@cn.fujitsu.com \
--to=tangchen@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=jacob.shin@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®