Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Peter Zijlstra
On Thu, Jun 05, 2014 at 02:53:21PM +0200, Peter Zijlstra wrote: > On Thu, Jun 05, 2014 at 01:11:10PM +0200, Ingo Molnar wrote: > > Unfortunately even with the latest bits from you the breakage I > > reported weeks ago is not resolved: > > > > In file included from include/linux/spinlock_types.h:1

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Peter Zijlstra
On Thu, Jun 05, 2014 at 01:11:10PM +0200, Ingo Molnar wrote: > Unfortunately even with the latest bits from you the breakage I > reported weeks ago is not resolved: > > In file included from include/linux/spinlock_types.h:15:0, > from kernel/bounds.c:14: > include/linux/spinlock_

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Peter Zijlstra
On Thu, Jun 05, 2014 at 02:35:12PM +0200, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > On Thu, Jun 05, 2014 at 01:11:10PM +0200, Ingo Molnar wrote: > > > Unfortunately even with the latest bits from you the breakage I > > > reported weeks ago is not resolved: > > > > crap, its the qrwl

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Ingo Molnar
* Peter Zijlstra wrote: > On Thu, Jun 05, 2014 at 01:11:10PM +0200, Ingo Molnar wrote: > > Unfortunately even with the latest bits from you the breakage I > > reported weeks ago is not resolved: > > crap, its the qrwlock bits, I fixed it for the config you gave me. > Some paravirt crap header

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Peter Zijlstra
On Thu, Jun 05, 2014 at 01:11:10PM +0200, Ingo Molnar wrote: > Unfortunately even with the latest bits from you the breakage I > reported weeks ago is not resolved: > crap, its the qrwlock bits, I fixed it for the config you gave me. Some paravirt crap header hell thing. Happen to have another .

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Ingo Molnar
* Ingo Molnar wrote: > Not unexpected the breakage comes from: > > 5627b9d439cc4dfaab738b8c21eef10fb40733f8 is the first bad commit > commit 5627b9d439cc4dfaab738b8c21eef10fb40733f8 > Author: Waiman Long > Date: Mon Feb 3 13:18:57 2014 +0100 > > x86, locking: Switch x86 to qrwlock-s

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Ingo Molnar
* Peter Zijlstra wrote: > On Thu, Jun 05, 2014 at 10:17:42AM +0200, Ingo Molnar wrote: > > > > Right now I'm somewhat 'missing' because I fell ill right when the > > merge window began :-/ But I merged all your pending bits shortly > > before the merge window started. During the merge window

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Peter Zijlstra
On Thu, Jun 05, 2014 at 10:17:42AM +0200, Ingo Molnar wrote: > > Ingo is 'missing' most of the time, so while I sit here with a > > massive queue of patches its nearly impossible for me to get > > anything merged :-( > > Right now I'm somewhat 'missing' because I fell ill right when the > merge

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Ingo Molnar
* Thomas Gleixner wrote: > On Thu, 5 Jun 2014, Ingo Molnar wrote: > > > > * Linus Torvalds wrote: > > > > > On Wed, Jun 4, 2014 at 10:22 AM, Peter Zijlstra > > > wrote: > > > > > > > > I _think_ tip/locking/core is empty and you could pull that into your > > > > tree without getting tons of

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Thomas Gleixner
On Thu, 5 Jun 2014, Ingo Molnar wrote: > > * Linus Torvalds wrote: > > > On Wed, Jun 4, 2014 at 10:22 AM, Peter Zijlstra > > wrote: > > > > > > I _think_ tip/locking/core is empty and you could pull that into your > > > tree without getting tons of extra weird stuff, but if you prefer a tree >

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Ingo Molnar
* Linus Torvalds wrote: > On Wed, Jun 4, 2014 at 10:22 AM, Peter Zijlstra wrote: > > > > I _think_ tip/locking/core is empty and you could pull that into your > > tree without getting tons of extra weird stuff, but if you prefer a tree > > based on your git tree I'll have to do some manual stuf

Re: [GIT PULL] locking tree changes for v3.16

2014-06-05 Thread Ingo Molnar
* Peter Zijlstra wrote: > On Tue, Jun 03, 2014 at 02:50:51PM -0700, Davidlohr Bueso wrote: > > On Tue, 2014-06-03 at 13:48 +0200, Ingo Molnar wrote: > > > Linus, > > > > > > Please pull the latest locking-core-for-linus git tree from: > > > > > >git://git.kernel.org/pub/scm/linux/kernel/gi

Re: [GIT PULL] locking tree changes for v3.16

2014-06-04 Thread Davidlohr Bueso
On Wed, 2014-06-04 at 14:22 -0700, Linus Torvalds wrote: > On Wed, Jun 4, 2014 at 10:22 AM, Peter Zijlstra wrote: > > > > I _think_ tip/locking/core is empty and you could pull that into your > > tree without getting tons of extra weird stuff, but if you prefer a tree > > based on your git tree I'

Re: [GIT PULL] locking tree changes for v3.16

2014-06-04 Thread Thomas Gleixner
On Wed, 4 Jun 2014, Linus Torvalds wrote: > On Wed, Jun 4, 2014 at 10:22 AM, Peter Zijlstra wrote: > > > > I _think_ tip/locking/core is empty and you could pull that into your > > tree without getting tons of extra weird stuff, but if you prefer a tree > > based on your git tree I'll have to do

Re: [GIT PULL] locking tree changes for v3.16

2014-06-04 Thread Linus Torvalds
On Wed, Jun 4, 2014 at 10:22 AM, Peter Zijlstra wrote: > > I _think_ tip/locking/core is empty and you could pull that into your > tree without getting tons of extra weird stuff, but if you prefer a tree > based on your git tree I'll have to do some manual stuff but that is > certainly possible.

Re: [GIT PULL] locking tree changes for v3.16

2014-06-04 Thread Peter Zijlstra
On Wed, Jun 04, 2014 at 09:17:20AM -0700, Linus Torvalds wrote: > On Wed, Jun 4, 2014 at 3:30 AM, Peter Zijlstra wrote: > > > > Ingo is 'missing' most of the time, so while I sit here with a massive > > queue of patches its nearly impossible for me to get anything merged :-( > > Ugh. I'd love to

Re: [GIT PULL] locking tree changes for v3.16

2014-06-04 Thread Linus Torvalds
On Wed, Jun 4, 2014 at 3:30 AM, Peter Zijlstra wrote: > > Ingo is 'missing' most of the time, so while I sit here with a massive > queue of patches its nearly impossible for me to get anything merged :-( Ugh. I'd love to get this whole locking stuff sorted out. At worst, could you just set up a g

Re: [GIT PULL] locking tree changes for v3.16

2014-06-04 Thread Peter Zijlstra
On Tue, Jun 03, 2014 at 02:50:51PM -0700, Davidlohr Bueso wrote: > On Tue, 2014-06-03 at 13:48 +0200, Ingo Molnar wrote: > > Linus, > > > > Please pull the latest locking-core-for-linus git tree from: > > > >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > > locking-core-for-linus

Re: [GIT PULL] locking tree changes for v3.16

2014-06-03 Thread Andrew Morton
On Tue, 03 Jun 2014 15:02:28 -0700 Davidlohr Bueso wrote: > On Tue, 2014-06-03 at 14:55 -0700, Andrew Morton wrote: > > On Tue, 03 Jun 2014 14:50:51 -0700 Davidlohr Bueso wrote: > > > > > > The main changes in this cycle were: > > > > > > > > - reduced/streamlined smp_mb__*() interface that a

Re: [GIT PULL] locking tree changes for v3.16

2014-06-03 Thread Davidlohr Bueso
On Tue, 2014-06-03 at 14:55 -0700, Andrew Morton wrote: > On Tue, 03 Jun 2014 14:50:51 -0700 Davidlohr Bueso wrote: > > > > The main changes in this cycle were: > > > > > > - reduced/streamlined smp_mb__*() interface that allows more usecases > > >and makes the existing ones less buggy, es

Re: [GIT PULL] locking tree changes for v3.16

2014-06-03 Thread Andrew Morton
On Tue, 03 Jun 2014 14:50:51 -0700 Davidlohr Bueso wrote: > > The main changes in this cycle were: > > > > - reduced/streamlined smp_mb__*() interface that allows more usecases > >and makes the existing ones less buggy, especially in rarer > >architectures > > > > - add rwsem implem

Re: [GIT PULL] locking tree changes for v3.16

2014-06-03 Thread Davidlohr Bueso
On Tue, 2014-06-03 at 13:48 +0200, Ingo Molnar wrote: > Linus, > > Please pull the latest locking-core-for-linus git tree from: > >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > locking-core-for-linus > ># HEAD: 3cf2f34e1a3d4d5ff209d087925cf950e52f4805 rwsem: Add comments t