linux-kernel - Re: [rfc 08/45] cpu alloc: x86 support

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.0711201607460.29220@schroedinger.engr.sgi.com>
Date:	Tue, 20 Nov 2007 16:10:45 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Andi Kleen <ak@...e.de>
cc:	akpm@...ux-foundation.org, travis@....com,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	linux-kernel@...r.kernel.org
Subject: Re: [rfc 08/45] cpu alloc: x86 support

On Tue, 20 Nov 2007, Christoph Lameter wrote:

> 32bit sign extension for what? Absolute data references? The addressing 
> that I have seen was IP relative. Thus I thought that the kernel could be 
> moved lower.

Argh. This is all depending on a special gcc option to compile the 
kernel and that option limits the kernel to the upper 2GB. So I guess for 
CPU_PTR we need to explicitly load the address as a constant, use that as 
a base and then add the offset and the smp_id shifted to it in the 
instruction. The CPU_INC/DEC stuff using gs is not affected.

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