From: "H. Peter Anvin" <hpa@zytor.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: rob@landley.net, tglx@linutronix.de,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
bhelgaas@google.com
Subject: Re: [PATCH 1/2 v2] x86: add max_addr boot option
Date: Mon, 11 Jun 2012 14:15:00 -0700 [thread overview]
Message-ID: <4FD65FD4.4060705@zytor.com> (raw)
In-Reply-To: <4FD5AFF2.3040306@cn.fujitsu.com>
On 06/11/2012 01:44 AM, Wen Congyang wrote:
> Currently, the boot option max_addr is only supported on ia64 platform.
> We also need it on x86 platform.
> For example:
> There are two nodes:
> NODE#0 address range 0x00000000 00000000 - 0x00010000 00000000
> NODE#1 address range 0x00010000 00000000 - 0x00020000 00000000
> If we only want to use node0, we can specify the max_addr. The boot
> option "mem=" can do the same thing now. But the boot option "mem="
> means the total memory used by the system. If we tell the user
> that the boot option "mem=" can do this, it will confuse the user.
> So we need an new boot option "max_addr" on x86 platform.
>
I fail to see what this does that cannot be done with the
since-long-existing memmap= option. Could you address why memmap=
doesn't match your needs?
-hpa
next prev parent reply other threads:[~2012-06-11 21:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 8:44 [PATCH 1/2 v2] x86: add max_addr boot option Wen Congyang
2012-06-11 8:46 ` [PATCH 2/2 v2] x86: reimplement mem " Wen Congyang
2012-06-11 17:35 ` [PATCH 1/2 v2] x86: add max_addr " Bjorn Helgaas
2012-06-12 6:29 ` Wen Congyang
2012-06-12 11:30 ` Bjorn Helgaas
2012-06-13 1:55 ` Kamezawa Hiroyuki
2012-06-13 4:59 ` Rob Landley
2012-06-14 2:06 ` Kamezawa Hiroyuki
2012-06-14 20:00 ` Rob Landley
2012-06-11 21:15 ` H. Peter Anvin [this message]
2012-06-12 6:26 ` Wen Congyang
2012-06-12 16:10 ` H. Peter Anvin
2012-06-13 2:21 ` Kamezawa Hiroyuki
2012-06-13 3:29 ` H. Peter Anvin
2012-06-13 5:20 ` Kamezawa Hiroyuki
2012-06-13 5:36 ` Wen Congyang
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=4FD65FD4.4060705@zytor.com \
--to=hpa@zytor.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=wency@cn.fujitsu.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox