From: Kasper Dupont <kasperd@daimi.au.dk>
To: Steven Rostedt <rostedt@stny.rr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Reserve memory from the command line
Date: Wed, 17 Jul 2002 22:38:58 +0200 [thread overview]
Message-ID: <3D35D5E2.1D1DBE41@daimi.au.dk> (raw)
In-Reply-To: <Pine.LNX.4.44.0207171307380.29293-100000@localhost.localdomain>
Steven Rostedt wrote:
>
> Hi,
>
> Today I just discoved that my Toshiba laptop has a small bit of bad
> memory. So I went on looking for a way to reserve the memory area from
> the command line, because I run several kernels for various reasons and
> that it would be easiest to just modify lilo.conf.
>
> After seaching the web and scanning the source code I realize that there
> are only patches to do this and not in the vanilla kernel. I was
> wondering why such a usefull feature is not in the kernel?
>
> I'm using kernel versions 2.4.7 to 2.4.18 and didn't want to go patching
> each one. I'll probably just hardcode the bad memory as reserved and be
> done with it.
>
> Is this feature planned on becoming part of the kernel, at least as a
> config option, and if not, then why not?
>
> If it is already there, and I missed it, please let me know.
I couldn't find it in the Documentation directory, but there
is a comment about it in linux/arch/i386/kernel/setup.c
/*
* "mem=nopentium" disables the 4MB page tables.
* "mem=XXX[kKmM]" defines a memory region from HIGH_MEM
* to <mem>, overriding the bios size.
* "mem=XXX[KkmM]@XXX[KkmM]" defines a memory region from
* <start> to <start>+<mem>, overriding the bios size.
*/
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razrep@daimi.au.dk
or mailto:mcxumhvenwblvtl@skrammel.yaboo.dk
prev parent reply other threads:[~2002-07-17 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 17:31 Steven Rostedt
2002-07-17 20:38 ` Kasper Dupont [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=3D35D5E2.1D1DBE41@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@stny.rr.com \
/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®