From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] s390 updates for final 7.1
Date: Thu, 11 Jun 2026 16:22:54 +0200 [thread overview]
Message-ID: <20260611142254.3501080A79-agordeev@linux.ibm.com> (raw)
Hi Linus,
please pull s390 updates for final 7.1.
Thanks,
Alexander Gordeev
The following changes since commit 7c6535c37dbc03c1c35926b7420d66fb122b513a:
s390: Implement _THIS_IP_ using inline asm (2026-05-30 11:33:32 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-7.1-5
for you to fetch changes up to 1f57f68c4dd101e5e8ffc9ffa6428f45bcdd776a:
s390: Remove GENERIC_LOCKBREAK Kconfig option (2026-06-08 18:59:07 +0200)
----------------------------------------------------------------
s390 fixes for final 7.1
- s390 selects GENERIC_LOCKBREAK when PREEMPT is enabled to tackle
an old compile error that no longer exists. Since recently PREEMPT
is always enabled, which causes massive performance regressions.
Remove GENERIC_LOCKBREAK from s390 Kconfig to fix the degradation.
----------------------------------------------------------------
Heiko Carstens (1):
s390: Remove GENERIC_LOCKBREAK Kconfig option
arch/s390/Kconfig | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index ecbcbb781e40..9921a3772bf7 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -29,9 +29,6 @@ config GENERIC_BUG
config GENERIC_BUG_RELATIVE_POINTERS
def_bool y
-config GENERIC_LOCKBREAK
- def_bool y if PREEMPTION
-
config AUDIT_ARCH
def_bool y
next reply other threads:[~2026-06-11 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 14:22 Alexander Gordeev [this message]
2026-06-11 20:58 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260611142254.3501080A79-agordeev@linux.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®