Re: Changing kernel configuration options related to the SquashFS
decompression
by Don Zickus
On Fri, Oct 02, 2020 at 04:12:46PM +0200, Bohdan Khomutskyi wrote:
> Hello Don,
>
> I filed a new merge request for this suggestion. It is now open at the
> following URI:
> https://gitlab.com/cki-project/kernel-ark/-/merge_requests/673
Perfect. Thanks! I see Justin already accepted it!
Cheers,
Don
>
> Kind regards,
>
> On 29/09/2020 16:34, Don Zickus wrote:
> > On Fri, Sep 18, 2020 at 10:49:09AM +0200, Bohdan Khomutskyi wrote:
> > > Hello,
> > >
> > > While working on the change proposal
> > > https://fedoraproject.org/wiki/Changes/OptimizeSquashFS
> > >
> > > I discovered that several kernel configuration options are set sub-optimally
> > > in Fedora. In RHEL 8, the optimal configuration is used.
> > > If we set those options to match RHEL 8, a performance improvement could be
> > > achieved while reading the SquashFS filesystem.
> > >
> > > Below you can see an excerpt from the configuration help:
> > Would you be willing to submit a merge request with these changes for
> > Fedora? Then we can have a discussion and review.
> >
> > Cheers,
> > Don
> >
> > > Set in RHEL 8:
> > >
> > > SQUASHFS_FILE_DIRECT
> > > ÃÂ ÃÂ ÃÂ ÃÂ Directly decompress file data into the page cache.
> > > ÃÂ ÃÂ ÃÂ ÃÂ Doing so can significantly improve performance because
> > > ÃÂ ÃÂ ÃÂ ÃÂ it eliminates a memcpy and it also removes the lock contention
> > > ÃÂ ÃÂ ÃÂ ÃÂ on the single buffer.
> > >
> > > SQUASHFS_DECOMP_MULTI_PERCPU
> > > ÃÂ ÃÂ ÃÂ ÃÂ By default Squashfs uses a single decompressor but it gives
> > > ÃÂ ÃÂ ÃÂ ÃÂ poor performance on parallel I/O workloads when using multiple CPU
> > > ÃÂ ÃÂ ÃÂ ÃÂ machines due to waiting on decompressor availability.
> > >
> > > ÃÂ ÃÂ ÃÂ ÃÂ This decompressor implementation uses a maximum of one
> > > ÃÂ ÃÂ ÃÂ ÃÂ decompressor per core.ÃÂ It uses percpu variables to ensure
> > > ÃÂ ÃÂ ÃÂ ÃÂ decompression is load-balanced across the cores.
> > >
> > > Set in Fedora:
> > > SQUASHFS_DECOMP_SINGLE
> > > ÃÂ ÃÂ ÃÂ ÃÂ Traditionally Squashfs has used single-threaded decompression.
> > > ÃÂ ÃÂ ÃÂ ÃÂ Only one block (data or metadata) can be decompressed at any
> > > ÃÂ ÃÂ ÃÂ ÃÂ one time.ÃÂ This limits CPU and memory usage to a minimum.
> > >
> > > SQUASHFS_FILE_CACHE
> > > ÃÂ ÃÂ ÃÂ ÃÂ Decompress file data into an intermediate buffer and then
> > > ÃÂ ÃÂ ÃÂ ÃÂ memcopy it into the page cache.
> > >
> > > The SquashFS filesystem is used on installation medium. So making the change
> > > I propose should improve the user experience during installation. It should
> > > also improve the user experience while booting from Fedora Live image.
> > >
> > > Kind regards,
> > >
> > > --
> > > Bohdan Khomutskyi
> > > Software engineer
> > > Red Hat
> > > _______________________________________________
> > > kernel mailing list -- kernel(a)lists.fedoraproject.org
> > > To unsubscribe send an email to kernel-leave(a)lists.fedoraproject.org
> > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
>
> --
> Bohdan Khomutskyi
> Software engineer
> Red Hat
>
3 years, 6 months
[OS-BUILD PATCH] Set SquashFS decompression options for all flavors
to match
RHEL
by GitLab Bridge on behalf of bkhomuts
From: Bohdan Khomutskyi <bkhomuts(a)redhat.com>
I discovered that several kernel configuration options related to SquashFS decompression are set sub-optimally in Fedora. But the optimal configuration is used in RHEL 8.
If we set those options to match RHEL, a performance improvement could be achieved while reading from compressed SquashFS filesystem.
Please see my original message in Fedora kernel mailing list archive:
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject....
There you can find an excerpt from Linux documentation for the changed options.
I found the disparity while working on Fedora change proposal:
https://fedoraproject.org/wiki/Changes/OptimizeSquashFS
Signed-off-by: Bohdan Khomutskyi <bkhomuts(a)redhat.com>
---
.../{ark => common}/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU | 0
.../{ark => common}/generic/CONFIG_SQUASHFS_DECOMP_SINGLE | 0
.../configs/{ark => common}/generic/CONFIG_SQUASHFS_FILE_CACHE | 0
.../configs/{ark => common}/generic/CONFIG_SQUASHFS_FILE_DIRECT | 0
.../configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU | 1 -
redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_SINGLE | 1 -
redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_CACHE | 1 -
redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_DIRECT | 1 -
8 files changed, 4 deletions(-)
rename redhat/configs/{ark => common}/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU (100%)
rename redhat/configs/{ark => common}/generic/CONFIG_SQUASHFS_DECOMP_SINGLE (100%)
rename redhat/configs/{ark => common}/generic/CONFIG_SQUASHFS_FILE_CACHE (100%)
rename redhat/configs/{ark => common}/generic/CONFIG_SQUASHFS_FILE_DIRECT (100%)
delete mode 100644 redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
delete mode 100644 redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_SINGLE
delete mode 100644 redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_CACHE
delete mode 100644 redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_DIRECT
diff --git a/redhat/configs/ark/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU b/redhat/configs/common/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
similarity index 100%
rename from redhat/configs/ark/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
rename to redhat/configs/common/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
diff --git a/redhat/configs/ark/generic/CONFIG_SQUASHFS_DECOMP_SINGLE b/redhat/configs/common/generic/CONFIG_SQUASHFS_DECOMP_SINGLE
similarity index 100%
rename from redhat/configs/ark/generic/CONFIG_SQUASHFS_DECOMP_SINGLE
rename to redhat/configs/common/generic/CONFIG_SQUASHFS_DECOMP_SINGLE
diff --git a/redhat/configs/ark/generic/CONFIG_SQUASHFS_FILE_CACHE b/redhat/configs/common/generic/CONFIG_SQUASHFS_FILE_CACHE
similarity index 100%
rename from redhat/configs/ark/generic/CONFIG_SQUASHFS_FILE_CACHE
rename to redhat/configs/common/generic/CONFIG_SQUASHFS_FILE_CACHE
diff --git a/redhat/configs/ark/generic/CONFIG_SQUASHFS_FILE_DIRECT b/redhat/configs/common/generic/CONFIG_SQUASHFS_FILE_DIRECT
similarity index 100%
rename from redhat/configs/ark/generic/CONFIG_SQUASHFS_FILE_DIRECT
rename to redhat/configs/common/generic/CONFIG_SQUASHFS_FILE_DIRECT
diff --git a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU b/redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
deleted file mode 100644
index 123cbd7db973..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU is not set
diff --git a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_SINGLE b/redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_SINGLE
deleted file mode 100644
index 5978a504eaec..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_DECOMP_SINGLE
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SQUASHFS_DECOMP_SINGLE=y
diff --git a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_CACHE b/redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_CACHE
deleted file mode 100644
index 15b6bd660cf8..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_CACHE
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SQUASHFS_FILE_CACHE=y
diff --git a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_DIRECT b/redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_DIRECT
deleted file mode 100644
index 50eff586df28..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_SQUASHFS_FILE_DIRECT
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_SQUASHFS_FILE_DIRECT is not set
--
GitLab
3 years, 6 months
✅ PASS: Test report for kernel 5.8.13-200.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.8.13-200.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=52606150
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ⚡⚡⚡ Storage nvme - tcp
ppc64le:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 2:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
Host 3:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
s390x:
Host 1:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
🚧 ❌ Storage nvme - tcp
x86_64:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 3:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ❌ Storage nvme - tcp
Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-0.rc7.24.cki.fc33 (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: 5c2192e56818 - [redhat] kernel-5.9.0-0.rc7.20201002git60e720931556.23
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug
3 years, 6 months
[OS-BUILD PATCH] [redhat] New configs in drivers/pinctrl
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
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.
CONFIG_PINCTRL_JASPERLAKE:
This pinctrl driver provides an interface that allows configuring
of Intel Jasper Lake PCH pins and using them as GPIOs.
Symbol: PINCTRL_JASPERLAKE [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:114
Prompt: Intel Jasper Lake PCH pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_INTEL [=m]
---
CONFIG_PINCTRL_SM8250:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc TLMM block found on the Qualcomm
Technologies Inc SM8250 platform.
Symbol: PINCTRL_SM8250 [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:219
Prompt: Qualcomm Technologies Inc SM8250 pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_MSM [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PINCTRL_JASPERLAKE | 1 +
.../common/generic/CONFIG_PINCTRL_SM8250 | 1 +
.../generic/CONFIG_PINCTRL_JASPERLAKE | 18 ------------------
.../generic/CONFIG_PINCTRL_SM8250 | 19 -------------------
4 files changed, 2 insertions(+), 37 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PINCTRL_JASPERLAKE
create mode 100644 redhat/configs/common/generic/CONFIG_PINCTRL_SM8250
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PINCTRL_JASPERLAKE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PINCTRL_SM8250
diff --git a/redhat/configs/common/generic/CONFIG_PINCTRL_JASPERLAKE b/redhat/configs/common/generic/CONFIG_PINCTRL_JASPERLAKE
new file mode 100644
index 000000000000..09f84c415cfe
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PINCTRL_JASPERLAKE
@@ -0,0 +1 @@
+# CONFIG_PINCTRL_JASPERLAKE is not set
diff --git a/redhat/configs/common/generic/CONFIG_PINCTRL_SM8250 b/redhat/configs/common/generic/CONFIG_PINCTRL_SM8250
new file mode 100644
index 000000000000..490872420c0e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PINCTRL_SM8250
@@ -0,0 +1 @@
+# CONFIG_PINCTRL_SM8250 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_JASPERLAKE b/redhat/configs/pending-common/generic/CONFIG_PINCTRL_JASPERLAKE
deleted file mode 100644
index 59ec9a1e7484..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_JASPERLAKE
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_PINCTRL_JASPERLAKE:
-#
-# This pinctrl driver provides an interface that allows configuring
-# of Intel Jasper Lake PCH pins and using them as GPIOs.
-#
-# Symbol: PINCTRL_JASPERLAKE [=n]
-# Type : tristate
-# Defined at drivers/pinctrl/intel/Kconfig:114
-# Prompt: Intel Jasper Lake PCH pinctrl and GPIO driver
-# Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
-# Location:
-# -> Device Drivers
-# -> Pin controllers (PINCTRL [=y])
-# Selects: PINCTRL_INTEL [=m]
-#
-#
-#
-# CONFIG_PINCTRL_JASPERLAKE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SM8250 b/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SM8250
deleted file mode 100644
index 383eb8bef202..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_SM8250
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_PINCTRL_SM8250:
-#
-# This is the pinctrl, pinmux, pinconf and gpiolib driver for the
-# Qualcomm Technologies Inc TLMM block found on the Qualcomm
-# Technologies Inc SM8250 platform.
-#
-# Symbol: PINCTRL_SM8250 [=n]
-# Type : tristate
-# Defined at drivers/pinctrl/qcom/Kconfig:219
-# Prompt: Qualcomm Technologies Inc SM8250 pin controller driver
-# Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Pin controllers (PINCTRL [=y])
-# Selects: PINCTRL_MSM [=y]
-#
-#
-#
-# CONFIG_PINCTRL_SM8250 is not set
--
2.26.2
3 years, 6 months
[OS-BUILD PATCH] [redhat] New configs in drivers/thermal
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
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.
CONFIG_THERMAL_NETLINK:
The thermal framework has a netlink interface to do thermal
zones discovery, temperature readings and events such as
trip point crossed, cooling device update or governor
change. It is recommended to enable the feature.
Symbol: THERMAL_NETLINK [=n]
Type : bool
Defined at drivers/thermal/Kconfig:20
Prompt: Thermal netlink management
Depends on: THERMAL [=y] && NET [=y]
Location:
-> Device Drivers
-> Thermal drivers (THERMAL [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_THERMAL_NETLINK | 1 +
.../generic/CONFIG_THERMAL_NETLINK | 19 -------------------
2 files changed, 1 insertion(+), 19 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_THERMAL_NETLINK
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_THERMAL_NETLINK
diff --git a/redhat/configs/common/generic/CONFIG_THERMAL_NETLINK b/redhat/configs/common/generic/CONFIG_THERMAL_NETLINK
new file mode 100644
index 000000000000..8abdc692a524
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_THERMAL_NETLINK
@@ -0,0 +1 @@
+# CONFIG_THERMAL_NETLINK is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_THERMAL_NETLINK b/redhat/configs/pending-common/generic/CONFIG_THERMAL_NETLINK
deleted file mode 100644
index 72adf3600dd2..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_THERMAL_NETLINK
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_THERMAL_NETLINK:
-#
-# The thermal framework has a netlink interface to do thermal
-# zones discovery, temperature readings and events such as
-# trip point crossed, cooling device update or governor
-# change. It is recommended to enable the feature.
-#
-# Symbol: THERMAL_NETLINK [=n]
-# Type : bool
-# Defined at drivers/thermal/Kconfig:20
-# Prompt: Thermal netlink management
-# Depends on: THERMAL [=y] && NET [=y]
-# Location:
-# -> Device Drivers
-# -> Thermal drivers (THERMAL [=y])
-#
-#
-#
-# CONFIG_THERMAL_NETLINK is not set
--
GitLab
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-0.rc7.23.cki.fc33 (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: 890ec7e1579a - [redhat] kernel-5.9.0-0.rc7.20201001git02de58b24d2e.22
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=kabidw_base --without=debug
3 years, 6 months