On 12/03/25 17:29, Dietmar Eggemann wrote: > On 12/03/2025 15:11, Juri Lelli wrote: > > On 12/03/25 09:55, Waiman Long wrote: > >> On 3/12/25 6:09 AM, Juri Lelli wrote: > >>> On 12/03/25 10:53, Dietmar Eggemann wrote: > >>>> On 11/03/2025 15:51, Waiman Long wrote: > > [...] > > >>> I unfortunately very much suspect !CPUSETS accounting is broken. But if > >>> that is indeed the case, it has been broken for a while. :( > >> Without CONFIG_CPUSETS, there will be one and only one global sched domain. > >> Will this still be a problem? > > > > Still need to double check. But I have a feeling we don't restore > > accounting correctly (at all?!) without CPUSETS. Orthogonal to this > > issue though, as if we don't, we didn't so far. :/ > > As expected: > > Since dl_rebuild_rd_accounting() is empty with !CONFIG_CPUSETS, the same > issue happens. Right, suspicion confirmed. :) But, as I was saying, I believe it has been broken for a while/forever. Not only suspend/resume, the accounting itself. Would you be OK if we address the !CPUSETS case with a separate later series? Thanks! Juri
