linux-kernel - Re: [PATCH v3 0/2] qspinlock: Introducing a 4-byte queue spinlock

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: <52EA139C.8040106@linux.vnet.ibm.com>
Date:	Thu, 30 Jan 2014 14:25:56 +0530
From:	Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com>
To:	Waiman Long <Waiman.Long@...com>
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, Arnd Bergmann <arnd@...db.de>,
	linux-arch@...r.kernel.org, x86@...nel.org,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michel Lespinasse <walken@...gle.com>,
	Andi Kleen <andi@...stfloor.org>,
	Rik van Riel <riel@...hat.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	George Spelvin <linux@...izon.com>,
	Tim Chen <tim.c.chen@...ux.intel.com>,
	Daniel J Blueman <daniel@...ascale.com>,
	Alexander Fyodorov <halcy@...dex.ru>,
	Aswin Chandramouleeswaran <aswin@...com>,
	Scott J Norton <scott.norton@...com>,
	Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@...com>
Subject: Re: [PATCH v3 0/2] qspinlock: Introducing a 4-byte queue spinlock

On 01/28/2014 11:49 PM, Waiman Long wrote:
> v2->v3:
>   - Simplify the code by using numerous mode only without an unfair option.
>   - Use the latest smp_load_acquire()/smp_store_release() barriers.
>   - Move the queue spinlock code to kernel/locking.
>   - Make the use of queue spinlock the default for x86-64 without user
>     configuration.
>   - Additional performance tuning.
>

Could you please point me to any dependency patches I am missing?
I am getting the compilation error (latest linus tree with 
9b0cd304f26b9fca140de15deeac2bf357d1f388)

Got something like below

make[1]: Nothing to be done for `all'.
   CHK     include/config/kernel.release
   CHK     include/generated/uapi/linux/version.h
   CHK     include/generated/utsrelease.h
make[1]: Nothing to be done for `relocs'.
   CC      kernel/bounds.s
In file included from include/asm-generic/getorder.h:7:0,
                  from /test/master/arch/x86/include/asm/page.h:71,
                  from /test/master/arch/x86/include/asm/processor.h:17,
                  from /test/master/arch/x86/include/asm/atomic.h:6,
                  from include/linux/atomic.h:4,
                  from include/asm-generic/qspinlock.h:22,
                  from 
/test/master/arch/x86/include/asm/spinlock_types.h:15,
                  from 
/test/master/arch/x86/include/asm/paravirt_types.h:331,
                  from /test/master/arch/x86/include/asm/ptrace.h:65,
                  from /test/master/arch/x86/include/asm/alternative.h:8,
                  from /test/master/arch/x86/include/asm/bitops.h:16,
                  from include/linux/bitops.h:33,
                  from include/linux/kernel.h:10,
                  from include/asm-generic/bug.h:13,
                  from /test/master/arch/x86/include/asm/bug.h:38,
                  from include/linux/bug.h:4,
                  from include/linux/page-flags.h:9,
                  from kernel/bounds.c:9:
include/linux/log2.h: In function ‘__ilog2_u32’:
include/linux/log2.h:34:2: error: implicit declaration of function ‘fls’ 
[-Werror=implicit-function-declaration]
include/linux/log2.h: In function ‘__ilog2_u64’:
include/linux/log2.h:42:2: error: implicit declaration of function 
‘fls64’ [-Werror=implicit-function-declaration]
include/linux/log2.h: In function ‘__roundup_pow_of_two’:
.
.
[trimmed]

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