[OS-BUILD PATCH] redhat/configs: Adjust CONFIG_MARCH and CONFIG_TUNE for s390x

[Mete Durlu (via Email Bridge)]

From: Mete Durlu

redhat/configs: Adjust CONFIG_MARCH and CONFIG_TUNE for s390x

JIRA: https://issues.redhat.com/browse/RHEL-86680

Upstream Status: RHEL only

Adjust kernel optimization/tuning for s390x latest machine generation.

Signed-off-by: Mete Durlu

diff --git a/redhat/configs/rhel/generic/s390x/CONFIG_MARCH_Z14 b/redhat/configs/rhel/generic/s390x/CONFIG_MARCH_Z14
index blahblah..blahblah 100644
--- a/redhat/configs/rhel/generic/s390x/CONFIG_MARCH_Z14
+++ b/redhat/configs/rhel/generic/s390x/CONFIG_MARCH_Z14
@@ -1 +1 @@
-CONFIG_MARCH_Z14=y
+# CONFIG_MARCH_Z14 is not set
diff --git a/redhat/configs/rhel/generic/s390x/CONFIG_MARCH_Z16 b/redhat/configs/rhel/generic/s390x/CONFIG_MARCH_Z16
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/rhel/generic/s390x/CONFIG_MARCH_Z16
@@ -0,0 +1 @@
+CONFIG_MARCH_Z16=y
diff --git a/redhat/configs/rhel/generic/s390x/CONFIG_TUNE_Z15 b/redhat/configs/rhel/generic/s390x/CONFIG_TUNE_Z15
index blahblah..blahblah 100644
--- a/redhat/configs/rhel/generic/s390x/CONFIG_TUNE_Z15
+++ b/redhat/configs/rhel/generic/s390x/CONFIG_TUNE_Z15
@@ -1 +1 @@
-CONFIG_TUNE_Z15=y
+# CONFIG_TUNE_Z15 is not set
diff --git a/redhat/configs/rhel/generic/s390x/CONFIG_TUNE_Z16 b/redhat/configs/rhel/generic/s390x/CONFIG_TUNE_Z16
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/rhel/generic/s390x/CONFIG_TUNE_Z16
@@ -0,0 +1 @@
+CONFIG_TUNE_Z16=y

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3831

[Daniel Horak (via Email Bridge)]

From: Daniel Horak on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3831#note_2457025...

I believe the agreement is to keep march on z14, but set mtune to z16, not
completely move both to z16.

[Mete Durlu (via Email Bridge)]

From: Mete Durlu on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3831#note_2457739...

Oops, I must have misread the issue description. Sorry about that, updating
now