From: tip-bot for Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
cascardo@holoscopio.com, tglx@linutronix.de
Subject: [tip:x86/mm] x86: Do not reserve brk for DMI if it's not going to be used
Date: Thu, 25 Feb 2010 10:10:35 GMT [thread overview]
Message-ID: <tip-e808bae2407a087bfd40200a27587898e5a9909d@git.kernel.org> (raw)
In-Reply-To: <1265758732-19320-1-git-send-email-cascardo@holoscopio.com>
Commit-ID: e808bae2407a087bfd40200a27587898e5a9909d
Gitweb: http://git.kernel.org/tip/e808bae2407a087bfd40200a27587898e5a9909d
Author: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
AuthorDate: Tue, 9 Feb 2010 21:38:45 -0200
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Thu, 25 Feb 2010 10:28:18 +0100
x86: Do not reserve brk for DMI if it's not going to be used
This will save 64K bytes from memory when loading linux if DMI is
disabled, which is good for embedded systems.
Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
LKML-Reference: <1265758732-19320-1-git-send-email-cascardo@holoscopio.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
arch/x86/kernel/setup.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 3499b4f..cb42109 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -121,7 +121,9 @@
unsigned long max_low_pfn_mapped;
unsigned long max_pfn_mapped;
+#ifdef CONFIG_DMI
RESERVE_BRK(dmi_alloc, 65536);
+#endif
unsigned int boot_cpu_id __read_mostly;
prev parent reply other threads:[~2010-02-25 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 23:38 [PATCH] x86: do not reserve brk for DMI if it's not going to be used Thadeu Lima de Souza Cascardo
2010-02-17 19:52 ` [tip:x86/mm] x86: Do " tip-bot for Thadeu Lima de Souza Cascardo
2010-02-25 10:10 ` tip-bot for Thadeu Lima de Souza Cascardo [this message]
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=tip-e808bae2407a087bfd40200a27587898e5a9909d@git.kernel.org \
--to=cascardo@holoscopio.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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