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: <20071115.185854.85318344.davem@davemloft.net>
Date:	Thu, 15 Nov 2007 18:58:54 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	clameter@....com
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

From: Christoph Lameter <clameter@....com>
Date: Thu, 15 Nov 2007 18:55:21 -0800 (PST)

> On Thu, 15 Nov 2007, David Miller wrote:
> 
> > 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.

There is assembler code to write, which as I stated several
times nobody is going to work on or test.

It is unreasonable to add this new VMEMMAP requirement in order for
your patches to work properly.

> > 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.

Someone has to implement and test VMEMMAP now on all of these
architectures, it is becomming a requirement unlike in the sparsemem
patches case where it was optional.

That's unreasonable.
-
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/