On 31/03/2022 16:53, Phil Auld wrote:
On Thu, Mar 31, 2022 at 04:37:50PM +0200 Dietmar Eggemann wrote:
quoted
On 31/03/2022 15:21, Phil Auld wrote:
quoted
On Thu, Mar 31, 2022 at 11:04:31AM +0200 Dietmar Eggemann wrote:
quoted
On 30/03/2022 17:56, Phil Auld wrote:
[...]
quoted
Yeah, maybe, it wouldn't hurt I guess. IMHO mentioning stress-ng's prctl
needs PR_SCHED_CORE support could also be handy since today's stress-ng
packages don't seem to have this yet.
My scripts clone it so I did not realize that was not in prepackaged versions
yet. But that said, that's really just a way to tickle the problem. Anyone
using core scheduling on such a system will hit this (at least the WARN part,
the actual crash was harder to create w/o all the threads and tasks stress-ng
uses).
OK.
I just saw that there is even a kselftest for this:
9f2699007493 - kselftest: Add test for core sched prctl interface
(2021-05-12 Chris Hyser)
But it doesn't trigger the issue.
I can send a v3 with a further commit message update.
Sounds good.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel