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.0711201334170.27539@schroedinger.engr.sgi.com>
Date:	Tue, 20 Nov 2007 13:34:53 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Andi Kleen <ak@...e.de>, 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, H. Peter Anvin wrote:

> But you wouldn't actually *use* this address space.  It's just for the linker
> to know what address to tag the references with; it gets relocated by gs_base
> down into proper kernel space.  The linker can stash the initialized reference
> copy at any address (LMA) which can be different from what it will be used at
> (VMA); that is not an issue.

That is already provided by this patchset. The cpu area starts at absolute 
0.
 
> To use %rip references, though, which are more efficient, you probably want to
> use offsets that are just below .text (at -2 GB); presumably
> -2 GB-[max size of percpu section].  Again, however, no CPU actually needs to
> have its data stashed in that particular location; it's just an offset.

Right. That is what we are discussion in another thread.

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