linux-kernel - Re: [patch 01/28] cpu alloc: The allocator

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0711151851420.32046@schroedinger.engr.sgi.com>
Date:	Thu, 15 Nov 2007 18:55:21 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	David Miller <davem@...emloft.net>
cc:	corbet@....net, andi@...stfloor.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, dada1@...mosbay.com,
	schwidefsky@...ibm.com
Subject: Re: [patch 01/28] cpu alloc: The allocator

On Thu, 15 Nov 2007, David Miller wrote:

> If you're talking about the VMEMMAP thing, that patch didn't remove
> the problem, it simply added optimizations for sparc64 so that you could
> sweep the problem under the rug.

The virtual mapping of the cpu areas is used by the patch I 
posted for i386, ia64 and x86_64. All the ones that I have access to here.

> Sparc32 is still broken, as just one of several possible examples.

I have not looked at sparc32 sorry. If you simply set up a couple of 
configuration values in arch/sparc32/Kconfig then everything will be fine.

> The BSS usage is still there for platforms that don't use VMEMMAP.

All MMU platforms can use the virtual mappings. The main use of the static 
configuration is for embedded systems.
-
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/