From mboxrd@z Thu Jan 1 00:00:00 1970 From: Waiman Long Date: Mon, 25 Oct 2021 18:25:32 +0000 Subject: Re: [PATCH] locking: remove spin_lock_flags() etc Message-Id: List-Id: References: <20211022120058.1031690-1-arnd@kernel.org> <2413f412-a390-bbc0-e848-e2a77d1f0ab3@redhat.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Arnd Bergmann Cc: Peter Zijlstra , Ingo Molnar , Will Deacon , Arnd Bergmann , Boqun Feng , Jonas Bonn , Stefan Kristiansson , Stafford Horne , "James E.J. Bottomley" , Helge Deller , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Heiko Carstens , Vasily Gorbik , Christian Borntraeger , Alexander Gordeev , Linux Kernel Mailing List , linux-ia64@vger.kernel.org, Openrisc , Parisc List , linuxppc-dev , linux-s390 On 10/25/21 11:44 AM, Arnd Bergmann wrote: > On Mon, Oct 25, 2021 at 5:28 PM Waiman Long wrote: >> On 10/25/21 9:06 AM, Arnd Bergmann wrote: >>> On s390, we pick between the cmpxchg() based directed-yield when >>> running on virtualized CPUs, and a normal qspinlock when running on a >>> dedicated CPU. >> I am not aware that s390 is using qspinlocks at all as I don't see >> ARCH_USE_QUEUED_SPINLOCKS being set anywhere under arch/s390. I only see >> that it uses a cmpxchg based spinlock. > Sorry, I should not have said "normal" here. See arch/s390/lib/spinlock.c > for their custom queued spinlocks as implemented in arch_spin_lock_queued(). > I don't know if that code actually does the same thing as the generic qspinlock, > but it seems at least similar. Yes, you are right. Their queued lock code looks like a custom version of the pvqspinlock code. Cheers, Longman