kernel February 2021

kernel@lists.fedoraproject.org

24 participants
153 discussions

Re: Kernel version plans for Fedora 34 ?
by Justin Forbes 11 Feb '21

11 Feb '21

On Thu, Feb 11, 2021 at 1:01 PM Bastien Nocera <hadess(a)hadess.net> wrote: > > On Thu, 2021-02-11 at 19:32 +0100, Hans de Goede wrote: > <snip> > > So where do I submit these once backported ? Do I just add them to > > dist-git > > as before ? AFAIK 5.11 will be the first kernel-ark based Fedora > > kernel > > (at least 5.10 dist-git does not look ark based), right ? > > I recently wanted to do that for a Bluetooth patch, and this is how I > went about it, along with discussions that happened on the list: > https://gitlab.com/cki-project/kernel-ark/-/merge_requests/872 > > I don't know whether I would have needed to proceed to get this > particular patch into stable releases, like Fedora 33 though. > The Fedora stable branches are a bit different, in that they do not copy over to ELN, so it is a much less formal process. Basically either I take it or I don't. And that is typically determined by a) What is the upstream status? b) How invasive is the backport? c) What is it trying to solve? Justin

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/perf
by GitLab Bridge on behalf of redhat-patchlab 11 Feb '21

11 Feb '21

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_ARM_DMC620_PMU: Support for PMU events monitoring on the ARM DMC-620 memory controller. Symbol: ARM_DMC620_PMU [=n] Type : tristate Defined at drivers/perf/Kconfig:133 Prompt: Enable PMU support for the ARM DMC-620 memory controller Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> Performance monitor support --- Cc: Mark Salter <msalter(a)redhat.com> Cc: Mark Langsdorf <mlangsdo(a)redhat.com> Cc: Jeremy Linton <jlinton(a)redhat.com> Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_ARM_DMC620_PMU | 1 + .../generic/CONFIG_ARM_DMC620_PMU | 17 ----------------- 2 files changed, 1 insertion(+), 17 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU diff --git a/redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU b/redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU new file mode 100644 index 000000000000..a7163f24fe2d --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_ARM_DMC620_PMU @@ -0,0 +1 @@ +# CONFIG_ARM_DMC620_PMU is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU b/redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU deleted file mode 100644 index a086d46317e9..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_ARM_DMC620_PMU +++ /dev/null @@ -1,17 +0,0 @@ -# CONFIG_ARM_DMC620_PMU: -# -# Support for PMU events monitoring on the ARM DMC-620 memory -# controller. -# -# Symbol: ARM_DMC620_PMU [=n] -# Type : tristate -# Defined at drivers/perf/Kconfig:133 -# Prompt: Enable PMU support for the ARM DMC-620 memory controller -# Depends on: PERF_EVENTS [=y] && (ARM64 [=y] && ACPI [=y] || COMPILE_TEST [=n]) -# Location: -# -> Device Drivers -# -> Performance monitor support -# -# -# -# CONFIG_ARM_DMC620_PMU is not set -- GitLab

3 3

Latest 5.11 kernels are only build for rawhide/F35, not available for F34
by Hans de Goede 11 Feb '21

11 Feb '21

Hi Justin, F34 has branched, so now, e.g. this kernel: https://koji.fedoraproject.org/koji/buildinfo?buildID=1706039 Only has a fc35 tag and there is no kernel-5.11.0-0.rc7.20210210gite0756cfc7d7c.150 pkg with a fc34 tag. So I think we need a separate F34 build for this kernel, or at least for the next kernel. Regards, Hans

3 3

Re: Ars claims: Fedora 32 is sluggish
by Ondrej Mosnacek 11 Feb '21

11 Feb '21

On Thu, Feb 11, 2021 at 10:14 AM Viktor Ashirov <vashirov(a)redhat.com> wrote: > On Wed, Feb 3, 2021 at 5:54 PM Michael Catanzaro <mcatanzaro(a)gnome.org> wrote: >> >> Hi, >> >> Has anybody investigated Jim Salter's claims that Fedora 32 is slow to >> launch applications? Recent article: >> >> https://arstechnica.com/gadgets/2021/02/ubuntu-core-20-adds-secure-boot-wit… >> >> "in my experience, Fedora 32 is noticeably, demonstrably more sluggish >> to launch applications than Ubuntu is in general." >> >> Original article: >> >> https://arstechnica.com/gadgets/2020/05/linux-distro-review-fedora-workstat… >> >> Would be good to know, for starters, whether this difference is real >> and measurable. > > This was bugging me for a while. I also noticed that Fedora 32 is a bit slower than it used to be. Compilation time of a project that I'm working on went from ~35-36 seconds to ~47-48. At first I thought that it's just another round of CPU vulnerabilities mitigations that introduced a performance drop. But after some digging I found that the default CPU governor was switched from 'ondemand' to 'schedutil' in Fedora kernel 5.9.7: > https://src.fedoraproject.org/rpms/kernel/c/73c86ebaee23df8310b903c1dab2176… > (see configs/fedora/generic/CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL) > > I switched it back using cpupower from kernel-tools: > $ sudo cpupower frequency-set --governor ondemand > > And confirmed that my compilation time went back to the previous ~35 seconds. > In the end I switched the governor to 'performance' and shaved another 5 seconds. And gnome-shell no longer feels sluggish, switching tabs in the browser is also instant. > To make the change permanent I used settings in /etc/sysconfig/cpupower and enabled cpupower service: > $ sudo systemctl enable --now cpupower.service > > The change of the default CPU governor looks pretty significant to me, but I couldn't find any discussions about it. CCing the Fedora kernel list and Justin. At the ARK tree level, the change was introduced in this commit, with no explanation: https://gitlab.com/cki-project/kernel-ark/commit/9d69ad49ab90db607e25a99eac… Justin, do you remember the reason for the change? Can/should it be reverted? -- Ondrej Mosnacek Software Engineer, Linux Security - SELinux kernel Red Hat, Inc.

3 2

✅ PASS: Test report for kernel 5.10.15-200.fc33 (fedora-33)
by CKI Project 11 Feb '21

11 Feb '21

Hello, We ran automated tests on the following kernel build: Kernel package: kernel-5.10.15-200.fc33 Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=61719970 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?prefi… 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) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng ppc64le: Host 1: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity Host 2: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test s390x: Host 1: ✅ Boot test 🚧 ✅ Storage blktests 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity x86_64: Host 1: ✅ Boot test 🚧 ✅ xfstests - ext4 🚧 ✅ xfstests - xfs 🚧 ✅ xfstests - btrfs 🚧 ✅ xfstests - nfsv4.2 🚧 ❌ xfstests - cifsv3.11 🚧 ✅ Storage blktests 🚧 ✅ Storage block - filesystem fio test 🚧 ✅ Storage block - queue scheduler test 🚧 ✅ Storage nvme - tcp 🚧 ✅ Storage: swraid mdadm raid_module test 🚧 ✅ stress: stress-ng Host 2: ✅ Boot test ✅ ACPI table test ✅ LTP ✅ Loopdev Sanity ✅ Memory: fork_mem ✅ Memory function: memfd_create ✅ AMTU (Abstract Machine Test Utility) 🚧 ✅ CIFS Connectathon 🚧 ✅ Ethernet drivers sanity 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 ⏱.

1 0

Self Introduction
by socrates bonomar 11 Feb '21

11 Feb '21

Hi, I'm from Southeast Africa, specifically Mozambique, last year I finished the study with BLFS, and I feel ready to support you in the development of this magnificent operating system. I have no problem handling unix tools, writing shell scripts (I like zsh), programming in C/C ++ among other things. I look forward to working with you for long periods of time.

1 0

[OS-BUILD PATCH] process_configs.sh: fix find/xargs data flow
by Ondrej Mosnáček (via Email Bridge) 11 Feb '21

11 Feb '21

From: Ondrej Mosnacek <omosnace(a)redhat.com> process_configs.sh: fix find/xargs data flow `xargs -0` expects arguments delimited by \0 on stdin, but instead it recieves a list of filenames delimited by \n from `find`. Fix that by adding `-print0` to `find` so that it outputs the filenames delimited by \0 as xargs expects. Signed-off-by: Ondrej Mosnacek <omosnace(a)redhat.com> diff a/redhat/configs/process_configs.sh b/redhat/configs/process_configs.sh --- a/redhat/configs/process_configs.sh +++ b/redhat/configs/process_configs.sh @@ -79,7 +79,7 @@ checkoptions() then while read -r LINE do - if find ./ -name "$(echo "$LINE" | awk -F "=" ' { print $1 } ' | awk ' { print $2 }')" | xargs -0 grep ^ | grep -q "process_configs_known_broken"; then + if find ./ -name "$(echo "$LINE" | awk -F "=" ' { print $1 } ' | awk ' { print $2 }')" -print0 | xargs -0 grep ^ | grep -q "process_configs_known_broken"; then # This is a known broken config. # See script help warning. checkoptions_error=false -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/885

2 5

[OS-BUILD PATCH] test, please ignore
by Don Zickus (via Email Bridge) 10 Feb '21

10 Feb '21

From: Don Zickus <dzickus(a)redhat.com> test, please ignore diff a/redhat/Makefile b/redhat/Makefile --- a/redhat/Makefile +++ b/redhat/Makefile @@ -1,4 +1,5 @@ GIT ?= git +# testing comment include Makefile.common include Makefile.rhpkg -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/892

1 0

[OS-BUILD PATCH 0/2] RHMAINTAINERS: Update for 20210209
by Prarit Bhargava (via Email Bridge) 10 Feb '21

10 Feb '21

From: Prarit Bhargava on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/890 Update for Feb 9 2021 Changes: 288cb5bb5524 (Waiman Long) RHMAINTAINERS: Add futex subsystem 6aa5c8637fd2 (Marcelo Ricardo Leitner) RHMAINTAINERS: NETWORKING: Add entry for Balazs Nemeth redhat/rhdocs/MAINTAINERS/RHMAINTAINERS | 12 ++++++++++++ 1 file changed, 12 insertions(+)

3 4

[OS-BUILD PATCH 0/4] Patch + Kconfig changes to prefer the SOF driver on Intel LPE audio hardware
by Hans de Goede (via Email Bridge) 10 Feb '21

10 Feb '21

From: Hans de Goede on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/889 This merge-req implements: https://fedoraproject.org/w/index.php?title=Changes/SofDefaultForIntelLp e It consists of 4 patches: 1. A patch making the preferred driver selectable in Kconfig, which is [already in -next](https://git.kernel.org/pub/scm/linux/kernel/git/tiwai /sound.git/commit/?h=for- next&id=5427c7d6296ee574037c4a6649ac45a9474d1f13) 2. Automatic creation of redhat/configs/pending-*/generic/CONFIG_SND_INTEL_BYT_PREFER_SOF files 3. Move the fedora CONFIG_SND_INTEL_BYT_PREFER_SOF config out of pending and enable it 4. Add a redhat/rebase-notes.txt with a reminder that on Fedora kernel rebases it should be disabled for F33 and older. Note I've left the rhel config for this in pending-rhel, leaving the decision of what to do with this up to the RHEL kernel folks. I believe that it makes sense to also enable this for RHEL. Intel LPE audio hardware is used in POS systems which are supported by RHEL and the SST driver will not be maintained anymore going forward, so for RHEL9 it is probably better to switch to the SOF driver which will actually see ongoing maintenance work upstream.

2 24

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel February 2021