[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52F2FCD9.3010402@hp.com>
Date: Wed, 05 Feb 2014 22:09:13 -0500
From: Waiman Long <waiman.long@...com>
To: Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.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 02/03/2014 03:51 AM, Raghavendra K T wrote:
> On 01/31/2014 12:19 AM, Raghavendra K T wrote:
>> On 01/30/2014 09:08 PM, Waiman Long wrote:
>>> On 01/30/2014 03:55 AM, Raghavendra K T wrote:
>>>> On 01/28/2014 11:49 PM, Waiman Long wrote:
>> [...]
>> 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]
>>>>
>>>
>>> The code will need to be compiled in either the latest linux tree as
>>> the
>>> patches have dependency on some new memory barrier that are in 3.14.
>>> Alternatively, you can compile with the latest tip tree.
>>>
>>> If you have already done that, please send me your config file so
>>> that I
>>> can reproduce the compilation error in my build environment.
>>>
>>
>> I did compile on latest linux tree which had barrier.txt. May be I 'll
>> recheck if I am missing something obvious.
>>
>> Here is .config attached
>
> An Update:
> The reason for failure was that I was compiling for guest. and
> CONFIG_PARAVIRT was enabled.
>
>
>
Thank for the information. I will update my patch to correct that problem.
-Longman
--
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