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

> 
> > This limitation shouldn't apply to the percpu area, since gs_base can be 
> > pointed anywhere in the address space -- in effect we're always indirect.
> 
> The initial reference copy of the percpu area has to be addressed by
> the linker.

Right that is important for the percpu references that can be folded by 
the linker in order to avoid address calculations.

> Hmm, in theory since it is not actually used by itself I suppose you could 
> move it into positive space.

But the positive space is reserved for a processes 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ