Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Celeste Liu <uwu@coelacanthus.name>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, guoren@kernel.org,
	anup@brainfault.org, heinrich.schuchardt@canonical.com,
	chenhuacai@kernel.org, kernel@xen0n.name,
	ysato@users.sourceforge.jp, dalias@libc.org,
	glaubitz@physik.fu-berlin.de, linux@armlinux.org.uk,
	florian.fainelli@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com, rjui@broadcom.com,
	sbranden@broadcom.com, tony@atomide.com,
	thierry.reding@gmail.com, jonathanh@nvidia.com,
	aaro.koskinen@iki.fi, andreas@kemnade.info, khilman@baylibre.com,
	rogerq@kernel.org, palmer@rivosinc.com,
	linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
	linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-tegra@vger.kernel.org, charlie@rivosinc.com,
	xry111@xry111.site, wahrenst@gmx.net, treding@nvidia.com
Subject: Re: [PATCH v4 0/4] defconfig: drop RT_GROUP_SCHED=y
Date: Thu, 30 Jan 2025 14:10:44 +0000	[thread overview]
Message-ID: <173824624400.971083.13259437466133760961.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250115-fix-riscv-rt_group_sched-v4-0-607606fe73a5@coelacanthus.name>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 15 Jan 2025 04:41:19 +0800 you wrote:
> For cgroup v1, if turned on, and there's any cgroup in the "cpu" hierarchy it
> needs an RT budget assigned, otherwise the processes in it will not be able to
> get RT at all. The problem with RT group scheduling is that it requires the
> budget assigned but there's no way we could assign a default budget, since the
> values to assign are both upper and lower time limits, are absolute, and need to
> be sum up to < 1 for each individal cgroup. That means we cannot really come up
> with values that would work by default in the general case.[1]
> 
> [...]

Here is the summary with links:
  - [v4,1/4] riscv: defconfig: drop RT_GROUP_SCHED=y
    https://git.kernel.org/riscv/c/26f2d6de4179
  - [v4,2/4] loongarch: defconfig: drop RT_GROUP_SCHED=y
    (no matching commit)
  - [v4,3/4] sh: defconfig: drop RT_GROUP_SCHED=y from sdk7786/urquell
    (no matching commit)
  - [v4,4/4] arm: defconfig: drop RT_GROUP_SCHED=y from bcm2835/tegra/omap2plus
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-01-30 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14 20:41 [PATCH v4 0/4] defconfig: drop RT_GROUP_SCHED=y Celeste Liu
2025-01-14 20:41 ` [PATCH v4 1/4] riscv: " Celeste Liu
2025-01-14 20:41 ` [PATCH v4 2/4] loongarch: " Celeste Liu
2025-01-14 20:41 ` [PATCH v4 3/4] sh: defconfig: drop RT_GROUP_SCHED=y from sdk7786/urquell Celeste Liu
2025-01-14 20:41 ` [PATCH v4 4/4] arm: defconfig: drop RT_GROUP_SCHED=y from bcm2835/tegra/omap2plus Celeste Liu
2025-01-16 18:04   ` Florian Fainelli
2025-03-06 19:19   ` Thierry Reding
2025-03-18 11:57     ` Huacai Chen
2025-03-21 12:28     ` Arnd Bergmann
2025-01-30 14:10 ` patchwork-bot+linux-riscv [this message]

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=173824624400.971083.13259437466133760961.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=andreas@kemnade.info \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=charlie@rivosinc.com \
    --cc=chenhuacai@kernel.org \
    --cc=dalias@libc.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=guoren@kernel.org \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=jonathanh@nvidia.com \
    --cc=kernel@xen0n.name \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=loongarch@lists.linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rjui@broadcom.com \
    --cc=rogerq@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=thierry.reding@gmail.com \
    --cc=tony@atomide.com \
    --cc=treding@nvidia.com \
    --cc=uwu@coelacanthus.name \
    --cc=wahrenst@gmx.net \
    --cc=xry111@xry111.site \
    --cc=ysato@users.sourceforge.jp \
    /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