linux-kernel - Re: [RESEND PATCH v2 1/2] update mem= option's spec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 11 Oct 2012 18:39:49 +0800
From:	Wen Congyang <wency@...fujitsu.com>
To:	hpa@...or.com
CC:	x86@...nel.org, linux-kernel@...r.kernel.org, rob@...dley.net,
	tglx@...utronix.de, mingo@...hat.com, bhelgaas@...gle.com
Subject: Re: [RESEND PATCH v2 1/2] update mem= option's spec

Hi, HPA

When do you have time to review this patchset?

Thanks
Wen Congyang

At 10/11/2012 06:38 PM, wency@...fujitsu.com Wrote:
> From: Wen Congyang <wency@...fujitsu.com>
> 
> 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 <wency@...fujitsu.com>
> Sort-of-tentatively-acked-by: Rob Landley <rob@...dley.net>
> 
> ---
>  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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/