From: Magnus Damm <magnus.damm@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] documentation - mem=
Date: Thu, 2 Dec 2004 00:41:22 +0100 [thread overview]
Message-ID: <aec7e5c304120115415153f706@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
Hi All,
I recently learnt that limiting RAM with by using only "mem=xxxM" is
no good on machines equipped with PCI. In my case (vanilla 2.6.9) the
cardbus bridge on my laptop got mapped to the unused RAM area which
resulted in wierd errors due to the collision.
The right solution is to use "mem=" together with "memmap=" to mark
the unused RAM area reserved.
>From now on I force the kernel to use 2016MiB by passing "mem=2016M
memmap=32M#2016M" instead of just "mem=2016M".
Anyway, this patch tried to document the behaviour. Please comment or apply.
Thanks!
/ magnus
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: linux-2.6.10-rc2-mm4-mem_hints.patch --]
[-- Type: text/x-patch; name="linux-2.6.10-rc2-mm4-mem_hints.patch", Size: 1905 bytes --]
diff -urN linux-2.6.10-rc2-mm4/Documentation/kernel-parameters.txt linux-2.6.10-rc2-mm4-mem_hints/Documentation/kernel-parameters.txt
--- linux-2.6.10-rc2-mm4/Documentation/kernel-parameters.txt 2004-12-01 23:50:53.125191440 +0100
+++ linux-2.6.10-rc2-mm4-mem_hints/Documentation/kernel-parameters.txt 2004-12-02 00:14:39.465354776 +0100
@@ -704,6 +704,9 @@
mem=nn[KMG] [KNL,BOOT] Force usage of a specific amount of memory
Amount of memory to be used when the kernel is not able
to see the whole system memory or for test.
+ [IA-32] Use together with memmap= to avoid physical
+ address space collisions. Without memmap= PCI devices
+ could be placed at addresses belonging to unused RAM.
mem=nopentium [BUGS=IA-32] Disable usage of 4MB pages for kernel
memory.
diff -urN linux-2.6.10-rc2-mm4/Documentation/memory.txt linux-2.6.10-rc2-mm4-mem_hints/Documentation/memory.txt
--- linux-2.6.10-rc2-mm4/Documentation/memory.txt 2004-10-18 23:55:36.000000000 +0200
+++ linux-2.6.10-rc2-mm4-mem_hints/Documentation/memory.txt 2004-12-02 00:03:01.712429344 +0100
@@ -21,6 +21,8 @@
All of these problems can be addressed with the "mem=XXXM" boot option
(where XXX is the size of RAM to use in megabytes).
It can also tell Linux to use less memory than is actually installed.
+If you use "mem=" on a machine with PCI, consider using "memmap=" to avoid
+physical address space collisions.
See the documentation of your boot loader (LILO, loadlin, etc.) about
how to pass options to the kernel.
@@ -44,7 +46,9 @@
* Disabling the cache from the BIOS.
* Try passing the "mem=4M" option to the kernel to limit
- Linux to using a very small amount of memory.
+ Linux to using a very small amount of memory. Use "memmap="-option
+ together with "mem=" on systems with PCI to avoid physical address
+ space collisions.
Other tricks:
reply other threads:[~2004-12-01 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aec7e5c304120115415153f706@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.