linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] x86: Use memblock_set_current_limit() to set limit for memblock.
@ 2013-08-14  3:44 Tang Chen
  2013-08-14  4:39 ` [tip:x86/mm] " tip-bot for Tang Chen
  2013-08-14  6:27 ` [PATCH] " Pekka Enberg
  0 siblings, 2 replies; 3+ messages in thread
From: Tang Chen @ 2013-08-14  3:44 UTC (permalink / raw)
  To: tglx, mingo, hpa, yinghai, penberg, jacob.shin; +Cc: x86, linux-kernel

In setup_arch() of x86, it set memblock.current_limit directly.
We should use memblock_set_current_limit(). If the implementation
is changed, it is easy to maintain.

Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
---
 arch/x86/kernel/setup.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index f8ec578..de33798 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -1070,7 +1070,7 @@ void __init setup_arch(char **cmdline_p)
 
 	cleanup_highmap();
 
-	memblock.current_limit = ISA_END_ADDRESS;
+	memblock_set_current_limit(ISA_END_ADDRESS);
 	memblock_x86_fill();
 
 	/*
@@ -1103,7 +1103,7 @@ void __init setup_arch(char **cmdline_p)
 
 	setup_real_mode();
 
-	memblock.current_limit = get_max_mapped();
+	memblock_set_current_limit(get_max_mapped());
 	dma_contiguous_reserve(0);
 
 	/*
-- 
1.7.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-08-14  6:37 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-14  3:44 [PATCH] x86: Use memblock_set_current_limit() to set limit for memblock Tang Chen
2013-08-14  4:39 ` [tip:x86/mm] " tip-bot for Tang Chen
2013-08-14  6:27 ` [PATCH] " Pekka Enberg

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).