On 09/26/2014 11:44 AM, Jiri Slaby wrote: > From: Christian Borntraeger <borntraeger@xxxxxxxxxx> > > 3.12-stable review patch. If anyone has any objections, please let me know. I just checked. It seems that the referenced commit 4badad352a6bb202ec68afa7a574c0bb961e5ebc (locking/mutex: Disable optimistic spinning on some architectures) is not part of 3.12-stable. So this fix is not (yet) necessary. This is probably also true for other stable backports. It seems that Kconfig just ignores non-existent entries for SELECT, so it does not hurt either. If you are going to backport that commit later on then it might make sense to keep this patch in, otherwise not. Christian > > > =============== > > commit 36e7fdaa1a04fcf65b864232e1af56a51c7814d6 upstream. > > commit 4badad352a6bb202ec68afa7a574c0bb961e5ebc (locking/mutex: Disable > optimistic spinning on some architectures) fenced spinning for > architectures without proper cmpxchg. > There is no need to disable mutex spinning on s390, though: > The instructions CS,CSG and friends provide the proper guarantees. > (We dont implement cmpxchg with locks). > > Signed-off-by: Christian Borntraeger <borntraeger@xxxxxxxxxx> > Cc: Ingo Molnar <mingo@xxxxxxxxxx> > Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx> > Signed-off-by: Heiko Carstens <heiko.carstens@xxxxxxxxxx> > Signed-off-by: Martin Schwidefsky <schwidefsky@xxxxxxxxxx> > Signed-off-by: Jiri Slaby <jslaby@xxxxxxx> > --- > arch/s390/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig > index 6671e8db1861..faa97bd4948e 100644 > --- a/arch/s390/Kconfig > +++ b/arch/s390/Kconfig > @@ -93,6 +93,7 @@ config S390 > select ARCH_INLINE_WRITE_UNLOCK_IRQ > select ARCH_INLINE_WRITE_UNLOCK_IRQRESTORE > select ARCH_SAVE_PAGE_KEYS if HIBERNATION > + select ARCH_SUPPORTS_ATOMIC_RMW > select ARCH_USE_CMPXCHG_LOCKREF > select ARCH_WANT_IPC_PARSE_VERSION > select BUILDTIME_EXTABLE_SORT > -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html