Github messages for voidlinux
 help / color / mirror / Atom feed
From: beadleha <beadleha@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Raspberry Pi images use powersave governor by default
Date: Sat, 13 Nov 2021 01:35:57 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34049@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]

New issue by beadleha on void-packages repository

https://github.com/void-linux/void-packages/issues/34049

Description:
The mainline Linux kernel uses `schedutil` as the default cpu frequency governor for both arm and arm64 since version 5.9, and now uses it by default on most other platforms as well. Void for x86/x86_64 currently use `schedutil` by default because of this. However, the Raspberry Pi kernel fork uses `powersave` instead, and then overrides it using the cpufreq package in Raspberry Pi OS. The developers do not seem inclined to change it since the default setting is overridden by Raspberry Pi OS anyway.

Void Linux does not initially override the default setting, so the default governor that the kernel is compiled with is the one that is used. This makes the system extremely slow until the user overrides the kernel's default setting.

My proposal is to add a sed command to the build templates make the kernel follow the default used in mainline kernels. This seems simpler than adding the cpufreq package to the base images. I believe the change would only affect the templates for `rpi-kernel`, `rpi3-kernel`, and `rpi4-kernel`.

And the change could look like this:
    # Set default frequency governor to match mainline kernel
    sed -i 's/CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=y/CONFIG_CPU_FREQ_DEFAULT_GOV_SCHEDUTIL=y/g' "$defconfig"

Let me know what you think.

### System

* xuname:  
Void 5.10.52_1 aarch64 Unknown notuptodate rFF
* package:  
rpi4-kernel-5.10.52_1

### Expected behavior
Linux mainline kernel uses `schedutil` by default, including on arm and arm64.
Void generally follows this default from upstream.
I would expect the default governor for Void to also be `schedutil` on my Raspberry Pi.

### Actual behavior
Void for Raspberry Pi uses `powersave` and the system is sluggish until the default is overridden.

### Steps to reproduce the behavior
Check default cpu governor on Void for Raspberry Pi. Compare to default for x86 and x86_64.

             reply	other threads:[~2021-11-13  0:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13  0:35 beadleha [this message]
2021-11-15  6:43 ` mikoxyz
2021-11-16  1:13 ` beadleha
2021-11-16  6:30 ` mikoxyz
2021-11-24 18:24 ` ahesford
2021-11-24 18:36 ` beadleha
2022-02-21  8:00 ` paper42
2022-06-12  2:16 ` github-actions
2022-06-27  2:14 ` [ISSUE] [CLOSED] " github-actions

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34049@inbox.vuxu.org \
    --to=beadleha@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).