From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Rick van Rein <rick@vanrein.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory
Date: Tue, 04 Mar 2008 08:29:36 -0800 [thread overview]
Message-ID: <47CD78F0.2060802@zytor.com> (raw)
In-Reply-To: <20080304133028.GC32383@elte.hu>
Ingo Molnar wrote:
>>>
>> How is this different from:
>>
>> memmap=<size>$<len>
>>
>> ... ?
>
> it's the inverse? When we identify bad areas of RAM, we really want to
> "punch holes" into the existing memory map. So 'badram=' or
> 'excludemem=' would be nicer and easier to use.
>
> Or extend 'memmap=' with an inverse parameter: memmap=!0x10000000$1M
> would exclude a 1MB region at 256MB physical.
>
My understanding is that the $-form (as opposed to the @-form or #-form)
is exactly that:
memmap=nn[KMG]$ss[KMG]
[KNL,ACPI] Mark specific memory as reserved.
Region of memory to be used, from ss to ss+nn.
"Reserved" usually means "don't use as either memory or free address space".
-hpa
next prev parent reply other threads:[~2008-03-04 16:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 13:42 [PATCH 2.6.24] mm: BadRAM support for broken memory Rick van Rein
2008-03-02 13:42 ` Rick van Rein
2008-03-02 17:01 ` KOSAKI Motohiro
2008-03-02 17:01 ` KOSAKI Motohiro
2008-03-02 17:42 ` Rick van Rein
2008-03-02 17:42 ` Rick van Rein
2008-03-03 3:21 ` KOSAKI Motohiro
2008-03-03 3:21 ` KOSAKI Motohiro
2008-03-03 5:32 ` Nick Piggin
2008-03-03 5:32 ` Nick Piggin
2008-03-03 7:14 ` KOSAKI Motohiro
2008-03-03 7:14 ` KOSAKI Motohiro
2008-03-03 7:35 ` Nick Piggin
2008-03-03 7:35 ` Nick Piggin
2008-03-03 9:49 ` KOSAKI Motohiro
2008-03-03 9:49 ` KOSAKI Motohiro
2008-03-03 9:58 ` KAMEZAWA Hiroyuki
2008-03-03 9:58 ` KAMEZAWA Hiroyuki
2008-03-02 17:53 ` Joseph Fannin
2008-03-02 19:34 ` Rick van Rein
2008-03-03 14:14 ` Pavel Machek
2008-03-03 16:41 ` KOSAKI Motohiro
2008-03-08 10:25 ` H. Peter Anvin
2008-03-08 10:30 ` H. Peter Anvin
2008-03-03 17:38 ` Randy Dunlap
2008-03-03 17:38 ` Randy Dunlap
[not found] ` <20080303082238.GB13580@elte.hu>
[not found] ` <47CC3005.5090706@zytor.com>
[not found] ` <20080304133028.GC32383@elte.hu>
2008-03-04 16:29 ` H. Peter Anvin [this message]
2008-03-04 16:47 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-03-04 12:21 devzero
2008-03-04 13:27 ` Ingo Molnar
2008-03-04 13:43 ` Rick van Rein
2008-03-04 14:06 ` Ingo Molnar
2008-03-04 15:05 ` Pavel Machek
2008-03-08 10:27 ` H. Peter Anvin
2008-03-08 11:13 ` Jiri Kosina
2008-03-10 10:12 ` Jan-Simon Möller
2008-03-10 11:24 ` Jan-Simon Möller
2008-03-10 11:52 ` Pavel Machek
2008-03-10 14:23 ` Jan-Simon Möller
2008-03-10 17:20 ` H. Peter Anvin
2008-03-10 17:48 ` Jan-Simon Möller
2008-03-10 18:59 ` Jan-Simon Möller
2008-03-10 19:16 ` Jan-Simon Möller
2008-03-10 22:56 ` Pavel Machek
2008-03-11 0:37 ` Jan-Simon Möller
2008-03-11 17:23 ` Len Brown
2008-03-11 17:49 ` Jan-Simon Möller
2008-03-11 19:24 ` Johannes Weiner
2008-03-11 20:00 ` Jan-Simon Möller
2008-03-10 22:07 ` Rick van Rein
2008-03-11 0:41 ` Jan-Simon Möller
2008-03-11 6:41 ` H. Peter Anvin
2008-03-04 14:00 devzero
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=47CD78F0.2060802@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rick@vanrein.org \
--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 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.