linux-kernel - Re: [PATCH v2 3/2] sched/deadline: Check bandwidth overflow earlier for hotplug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5a36a2e8-bd78-4875-9b9e-814468ca6692@arm.com>
Date: Fri, 7 Feb 2025 14:38:32 +0100
From: Dietmar Eggemann <dietmar.eggemann@....com>
To: Jon Hunter <jonathanh@...dia.com>, Juri Lelli <juri.lelli@...hat.com>
Cc: Thierry Reding <treding@...dia.com>, Waiman Long <longman@...hat.com>,
 Tejun Heo <tj@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
 Michal Koutny <mkoutny@...e.com>, Ingo Molnar <mingo@...hat.com>,
 Peter Zijlstra <peterz@...radead.org>,
 Vincent Guittot <vincent.guittot@...aro.org>,
 Steven Rostedt <rostedt@...dmis.org>, Ben Segall <bsegall@...gle.com>,
 Mel Gorman <mgorman@...e.de>, Valentin Schneider <vschneid@...hat.com>,
 Phil Auld <pauld@...hat.com>, Qais Yousef <qyousef@...alina.io>,
 Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
 "Joel Fernandes (Google)" <joel@...lfernandes.org>,
 Suleiman Souhlal <suleiman@...gle.com>, Aashish Sharma <shraash@...gle.com>,
 Shin Kawamura <kawasin@...gle.com>,
 Vineeth Remanan Pillai <vineeth@...byteword.org>,
 linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
 "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH v2 3/2] sched/deadline: Check bandwidth overflow earlier
 for hotplug

On 07/02/2025 11:38, Jon Hunter wrote:
> 
> On 06/02/2025 09:29, Juri Lelli wrote:
>> On 05/02/25 16:56, Jon Hunter wrote:
>>
>> ...
>>
>>> Thanks! That did make it easier :-)
>>>
>>> Here is what I see ...
>>
>> Thanks!
>>
>> Still different from what I can repro over here, so, unfortunately, I
>> had to add additional debug printks. Pushed to the same branch/repo.
>>
>> Could I ask for another run with it? Please also share the complete
>> dmesg from boot, as I would need to check debug output when CPUs are
>> first onlined.

So you have a system with 2 big and 4 LITTLE CPUs (Denver0 Denver1 A57_0
A57_1 A57_2 A57_3) in one MC sched domain and (Denver1 and A57_0) are
isol CPUs?

This should be easy to set up for me on my Juno-r0 [A53 A57 A57 A53 A53 A53]

[...]