From: Thomas Huth on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3830
While working on a merge request for Centos Stream (see
https://gitlab.com/redhat/centos-stream/src/kernel/centos-
stream-9/-/merge_requests/6695#note_2438236147 ) I noticed that some config
switches in kernel-ark are not set in an optimal way yet. So here are some
patches to get them fixed!
Signed-off-by: Thomas Huth <thuth(a)redhat.com>
---
redhat/configs/common/debug/s390x/CONFIG_KERNEL_IMAGE_BASE | 1 +
redhat/configs/fedora/generic/s390x/CONFIG_AP => redhat/configs/common/generic/s390x/CONFIG_AP | 0
redhat/configs/fedora/generic/s390x/CONFIG_KERNEL_IMAGE_BASE => redhat/configs/common/generic/s390x/CONFIG_KERNEL_IMAGE_BASE | 0
redhat/configs/fedora/debug/s390x/CONFIG_ZCRYPT_DEBUG | 1 -
redhat/configs/fedora/generic/s390x/CONFIG_ZCRYPT_DEBUG | 1 -
redhat/configs/rhel/debug/s390x/CONFIG_ZCRYPT_DEBUG | 1 -
redhat/configs/rhel/generic/s390x/CONFIG_ZCRYPT_DEBUG | 1 -
redhat/configs/rhel/generic/CONFIG_AP | 1 -
redhat/configs/rhel/generic/CONFIG_KERNEL_IMAGE_BASE | 1 -
9 files changed, 1 insertions(+), 6 deletions(-)
From: Scott Weaver on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3822
This enables Rust code in the ELN kernel, which requires enabling
CONFIG_EXTENDED_MODVERSIONS and CONFIG_GENDWARFKSYMS.
The DRM panic with QR code functionality is the first Rust based code to be
enabled. A QR code URL is not defined but we will likely want to update that
before enabling this in RHEL.
For now, the ipaclones-internal package is disabled because bindgen (libclang)
does not support gcc's `-fdump-ipa-clones`.
Signed-off-by: Scott Weaver <scweaver(a)redhat.com>
---
redhat/configs/fedora/generic/CONFIG_DRM_PANIC => redhat/configs/common/generic/CONFIG_DRM_PANIC | 0
redhat/configs/fedora/generic/CONFIG_DRM_PANIC_BACKGROUND_COLOR => redhat/configs/common/generic/CONFIG_DRM_PANIC_BACKGROUND_COLOR | 0
redhat/configs/fedora/generic/CONFIG_DRM_PANIC_DEBUG => redhat/configs/common/generic/CONFIG_DRM_PANIC_DEBUG | 0
redhat/configs/fedora/generic/CONFIG_DRM_PANIC_FOREGROUND_COLOR => redhat/configs/common/generic/CONFIG_DRM_PANIC_FOREGROUND_COLOR | 0
redhat/configs/fedora/generic/CONFIG_DRM_PANIC_SCREEN_QR_CODE => redhat/configs/common/generic/CONFIG_DRM_PANIC_SCREEN_QR_CODE | 0
redhat/configs/fedora/generic/CONFIG_DRM_PANIC_SCREEN_QR_VERSION => redhat/configs/common/generic/CONFIG_DRM_PANIC_SCREEN_QR_VERSION | 0
redhat/configs/common/generic/CONFIG_RUST | 2 +-
redhat/configs/common/generic/CONFIG_RUST_OVERFLOW_CHECKS | 2 +-
redhat/configs/fedora/generic/CONFIG_RUST | 1 -
redhat/configs/fedora/generic/CONFIG_RUST_OVERFLOW_CHECKS | 1 -
redhat/configs/rhel/generic/x86/CONFIG_SAMPLES_RUST | 1 +
redhat/configs/rhel/generic/CONFIG_DRM_PANIC | 1 -
redhat/configs/rhel/generic/CONFIG_DRM_PANIC_SCREEN | 1 +
redhat/configs/rhel/generic/CONFIG_DRM_PANIC_SCREEN_QR_CODE_URL | 1 +
redhat/configs/rhel/generic/CONFIG_EXTENDED_MODVERSIONS | 2 +-
redhat/configs/rhel/generic/CONFIG_GENDWARFKSYMS | 2 +-
redhat/configs/rhel/generic/CONFIG_MODVERSIONS | 2 +-
redhat/kernel.spec.template | 4 +---
18 files changed, 9 insertions(+), 11 deletions(-)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/hwtracing
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
Symbol: CORESIGHT_CTCU [=n]
Type : tristate
Defined at drivers/hwtracing/coresight/Kconfig:136
Prompt: CoreSight TMC Control Unit driver
Depends on: CORESIGHT [=m] && CORESIGHT_LINK_AND_SINK_TMC [=m]
Location:
-> Kernel hacking
-> arm64 Debugging
-> CoreSight Tracing Support (CORESIGHT [=m])
-> CoreSight TMC Control Unit driver (CORESIGHT_CTCU [=n])
Commit: f78d206f3d73 (Coresight: Add Coresight TMC Control Unit driver)
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff --git a/redhat/configs/pending-rhel/generic/CONFIG_CORESIGHT_CTCU b/redhat/configs/pending-rhel/generic/CONFIG_CORESIGHT_CTCU
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/pending-rhel/generic/CONFIG_CORESIGHT_CTCU
+++ /dev/null
@@ -1,15 +0,0 @@
-# Symbol: CORESIGHT_CTCU [=n]
-# Type : tristate
-# Defined at drivers/hwtracing/coresight/Kconfig:136
-# Prompt: CoreSight TMC Control Unit driver
-# Depends on: CORESIGHT [=m] && CORESIGHT_LINK_AND_SINK_TMC [=m]
-# Location:
-# -> Kernel hacking
-# -> arm64 Debugging
-# -> CoreSight Tracing Support (CORESIGHT [=m])
-# -> CoreSight TMC Control Unit driver (CORESIGHT_CTCU [=n])
-#
-#
-#
-# Commit: f78d206f3d73 (Coresight: Add Coresight TMC Control Unit driver)
-# CONFIG_CORESIGHT_CTCU is not set
diff --git a/redhat/configs/rhel/generic/CONFIG_CORESIGHT_CTCU b/redhat/configs/rhel/generic/CONFIG_CORESIGHT_CTCU
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/rhel/generic/CONFIG_CORESIGHT_CTCU
@@ -0,0 +1 @@
+CONFIG_CORESIGHT_CTCU=m
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3801
From: Jan Stancek <jstancek(a)redhat.com>
redhat/kernel.spec: fix duplicate packaging of ynl headers
It's currently packages by both kernel-headers and kernel-tools-libs-devel,
which requires them to be in sync, otherwise there's potential conflict
when user updates just one of them.
Fixes: eb3706d2d279 ("redhat: kernel.spec: add ynl to kernel-tools")
Signed-off-by: Jan Stancek <jstancek(a)redhat.com>
diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index blahblah..blahblah 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -3836,6 +3836,7 @@ fi\
%files headers
/usr/include/*
%exclude %{_includedir}/cpufreq.h
+%exclude %{_includedir}/ynl
%endif
%if %{with_cross_headers}
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3828
From: Jan Stancek <jstancek(a)redhat.com>
redhat/kernel.spec: fix duplicate packages of ynl headers
It's currently packages by both kernel-headers and kernel-tools-libs-devel,
which requires them to be in sync, otherwise there's potential conflict
when user updates just one of them.
Fixes: eb3706d2d279 ("redhat: kernel.spec: add ynl to kernel-tools")
Signed-off-by: Jan Stancek <jstancek(a)redhat.com>
diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index blahblah..blahblah 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -3836,6 +3836,7 @@ fi\
%files headers
/usr/include/*
%exclude %{_includedir}/cpufreq.h
+%exclude %{_includedir}/ynl
%endif
%if %{with_cross_headers}
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3828
Hi Fedora users, developers, and friends!
It's time to start thinking about Test Days for Fedora 43.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at
https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:
GNOME Test Day*
i18n Test Day*
Kernel Test Week(s)*
Upgrade Test Day*
IoT Test Week*
Cloud Test Day*
Fedora CoreOS Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on Libera[0]. Thanks!
[0] https://web.libera.chat/?channels=fedora-qa
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in arch/s390
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
Symbol: MARCH_Z17 [=n]
Type : bool
Defined at arch/s390/Kconfig:404
Prompt: IBM z17
Location:
-> Processor type and features
-> Processor type (<choice> [=n])
-> IBM z17 (MARCH_Z17 [=n])
Selects: HAVE_MARCH_Z17_FEATURES [=n]
Commit: c51ea9888e88 (s390: Allow to compile with z17 optimizations)
---
Symbol: TUNE_Z17 [=n]
Type : bool
Defined at arch/s390/Kconfig:482
Prompt: IBM z17
Location:
-> Processor type and features
-> Tune code generation (<choice> [=n])
-> IBM z17 (TUNE_Z17 [=n])
Commit: c51ea9888e88 (s390: Allow to compile with z17 optimizations)
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff --git a/redhat/configs/pending-rhel/generic/CONFIG_MARCH_Z17 b/redhat/configs/pending-rhel/generic/CONFIG_MARCH_Z17
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/pending-rhel/generic/CONFIG_MARCH_Z17
+++ /dev/null
@@ -1,14 +0,0 @@
-# Symbol: MARCH_Z17 [=n]
-# Type : bool
-# Defined at arch/s390/Kconfig:404
-# Prompt: IBM z17
-# Location:
-# -> Processor type and features
-# -> Processor type (<choice> [=n])
-# -> IBM z17 (MARCH_Z17 [=n])
-# Selects: HAVE_MARCH_Z17_FEATURES [=n]
-#
-#
-#
-# Commit: c51ea9888e88 (s390: Allow to compile with z17 optimizations)
-# CONFIG_MARCH_Z17 is not set
diff --git a/redhat/configs/pending-rhel/generic/CONFIG_TUNE_Z17 b/redhat/configs/pending-rhel/generic/CONFIG_TUNE_Z17
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/pending-rhel/generic/CONFIG_TUNE_Z17
+++ /dev/null
@@ -1,13 +0,0 @@
-# Symbol: TUNE_Z17 [=n]
-# Type : bool
-# Defined at arch/s390/Kconfig:482
-# Prompt: IBM z17
-# Location:
-# -> Processor type and features
-# -> Tune code generation (<choice> [=n])
-# -> IBM z17 (TUNE_Z17 [=n])
-#
-#
-#
-# Commit: c51ea9888e88 (s390: Allow to compile with z17 optimizations)
-# CONFIG_TUNE_Z17 is not set
diff --git a/redhat/configs/rhel/generic/CONFIG_MARCH_Z17 b/redhat/configs/rhel/generic/CONFIG_MARCH_Z17
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/rhel/generic/CONFIG_MARCH_Z17
@@ -0,0 +1 @@
+# CONFIG_MARCH_Z17 is not set
diff --git a/redhat/configs/rhel/generic/CONFIG_TUNE_Z17 b/redhat/configs/rhel/generic/CONFIG_TUNE_Z17
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/rhel/generic/CONFIG_TUNE_Z17
@@ -0,0 +1 @@
+# CONFIG_TUNE_Z17 is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/3827
Hi, we tested your kernel and here are the results:
Overall result: PASSED
Merge: OK
Compile: OK
Test: OK
Tested-by: CKI Project <cki-project(a)redhat.com>
Kernel information:
Brew / Koji Task ID: 131383742
You can find all the details about the test run at
https://datawarehouse.cki-project.org/kcidb/checkouts/redhat:koji-131383742
Tests that were not ran because of internal issues:
Boot test [s390x, x86_64]
CKI/restraint [s390x, x86_64]
machineinfo [s390x, x86_64]
Reboot test [s390x, x86_64]
SELinux Custom Module Setup [s390x, x86_64]
stress: stress-ng - cpu [s390x, x86_64]
stress: stress-ng - cpu-cache [s390x, x86_64]
stress: stress-ng - interrupt [s390x, x86_64]
stress: stress-ng - memory [s390x, x86_64]
If you find a failure unrelated to your changes, please ask the test maintainer to review it.
This will prevent the failures from being incorrectly reported in the future.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________