linux-kernel - Re: [GIT RFC] percpu: use dynamic percpu allocator as the default percpu 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]

Date:	Wed, 01 Apr 2009 01:37:02 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	schwidefsky@...ibm.com
Cc:	tj@...nel.org, mingo@...e.hu, rusty@...tcorp.com.au,
	tglx@...utronix.de, x86@...nel.org, linux-kernel@...r.kernel.org,
	hpa@...or.com, lethal@...ux-sh.org, rmk@....linux.org.uk,
	starvik@...s.com, ralf@...ux-mips.org, cooloney@...nel.org,
	kyle@...artin.ca, matthew@....cx, grundler@...isc-linux.org,
	takata@...ux-m32r.org, benh@...nel.crashing.org, rth@...ddle.net,
	ink@...assic.park.msu.ru, heiko.carstens@...ibm.com
Subject: Re: [GIT RFC] percpu: use dynamic percpu allocator as the default
 percpu allocator

From: Martin Schwidefsky <schwidefsky@...ibm.com>
Date: Wed, 1 Apr 2009 10:32:57 +0200

> The code sequence with @GOT:
> 
> 	larl	%r12,_GLOBAL_OFFSET_TABLE_
> 	lg	%r1,symbol@GOT(%r12)
> 
> is equivalent to:
> 
> 	larl	%r1,symbol@...ENT
> 	lg	%r1,0(%r1)
> 
> The advantage of the second code sequence is that it need a single
> register and the size of the GOT is not limited to 4K as in the first
> example (the offset in an RX format instruction is limited to 12 bits -
> but that is probably something you don't want to know ;-).

If practical I think you guys should just force all of the module
address space below 4GB virtually, as we do on sparc64.  It's a good
way to avoid all of these problems.
--
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/