[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150319183220.GU23123@twins.programming.kicks-ass.net>
Date: Thu, 19 Mar 2015 19:32:20 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: David Vrabel <david.vrabel@...rix.com>
Cc: Waiman.Long@...com, raghavendra.kt@...ux.vnet.ibm.com,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org, hpa@...or.com,
boris.ostrovsky@...cle.com, linux-arch@...r.kernel.org,
x86@...nel.org, mingo@...hat.com, doug.hatch@...com,
xen-devel@...ts.xenproject.org, paulmck@...ux.vnet.ibm.com,
riel@...hat.com, scott.norton@...com, paolo.bonzini@...il.com,
tglx@...utronix.de, virtualization@...ts.linux-foundation.org,
oleg@...hat.com, luto@...capital.net, torvalds@...ux-foundation.org
Subject: Re: [Xen-devel] [PATCH 0/9] qspinlock stuff -v15
On Thu, Mar 19, 2015 at 06:01:34PM +0000, David Vrabel wrote:
> This seems work for me, but I've not got time to give it a more thorough
> testing.
>
> You can fold this into your series.
Thanks!
> There doesn't seem to be a way to disable QUEUE_SPINLOCKS when supported by
> the arch, is this intentional? If so, the existing ticketlock code could go.
Yeah, its left as a rudiment such that if we find issues with the
qspinlock code we can 'revert' with a trivial patch. If no issues show
up we can rip out all the old code in a subsequent release.
--
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