Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758549Ab2JKKdG (ORCPT ); Thu, 11 Oct 2012 06:33:06 -0400 Received: from cn.fujitsu.com ([222.73.24.84]:38762 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1758478Ab2JKKdD (ORCPT ); Thu, 11 Oct 2012 06:33:03 -0400 X-IronPort-AV: E=Sophos;i="4.80,571,1344182400"; d="scan'208";a="5983666" From: wency@cn.fujitsu.com To: x86@kernel.org, linux-kernel@vger.kernel.org Cc: rob@landley.net, tglx@linutronix.de, mingo@redhat.com, bhelgaas@google.com, hpa@zytor.com, Wen Congyang Subject: [RESEND PATCH v2 1/2] update mem= option's spec Date: Thu, 11 Oct 2012 18:38:32 +0800 Message-Id: <1349951913-12485-1-git-send-email-wency@cn.fujitsu.com> X-Mailer: git-send-email 1.7.1 X-MIMETrack: Itemize by SMTP Server on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2012/10/11 18:32:49, Serialize by Router on mailserver/fnst(Release 8.5.3|September 15, 2011) at 2012/10/11 18:32:50, Serialize complete at 2012/10/11 18:32:50 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1674 Lines: 40 From: Wen Congyang Current mem= implementation seems buggy because specification and implementation doesn't match. Current mem= has been working for many years and it's not buggy, it works as expected. So we should update the specification. Signed-off-by: Wen Congyang Sort-of-tentatively-acked-by: Rob Landley --- Documentation/kernel-parameters.txt | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index a92c5eb..924b1a4 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1471,9 +1471,10 @@ bytes respectively. Such letter suffixes can also be entirely omitted. 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. - [X86-32] Use together with memmap= to avoid physical - address space collisions. Without memmap= PCI devices - could be placed at addresses belonging to unused RAM. + [X86-32] Work as limiting max address. 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=X86-32] Disable usage of 4MB pages for kernel memory. -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/