linux-kernel - [patch 0/2] Refactor spinlock inlining

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-next>] [day] [month] [year] [list]

Message-Id: <20091109150033.125758935@linutronix.de>
Date:	Mon, 09 Nov 2009 15:21:26 -0000
From:	Thomas Gleixner <tglx@...utronix.de>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: [patch 0/2] Refactor spinlock inlining

While moving preempt-rt to 2.6.32-rc I tripped over the spinlock
inlining changes and had a hard time to figure out when and which lock
function is inlined as the __always_inline__ defines are not directly
controlling the inlining because there are overrides depending on
various config options.

Merging the -rt modifications into this results in a horrible mess and
I tried to find a solution which simplifies the inlining decisions and
makes it more obvious when the decision is taken. 

To allow easier intergration of preempt-rt I reworked the inline
decision ifdeffery to be completely Kconfig based.

The result is slightly smaller in code lines, but adds a Kconfig file
which contains all the rules of inlining decisions. Architecturs can
select each locking function for inlining in the arch Kconfig instead
of defining __always_inline__*.

Thanks,

	tglx

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