From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Phil Auld <pauld@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arch/arm64: Fix topology initialization for core scheduling
Date: Thu, 31 Mar 2022 17:49:46 +0200 [thread overview]
Message-ID: <887fd1ba-c83f-77e4-74a9-53eef1dacc49@arm.com> (raw)
In-Reply-To: <20220331145343.GF17613@pauld.bos.csb>
On 31/03/2022 16:53, Phil Auld wrote:
> On Thu, Mar 31, 2022 at 04:37:50PM +0200 Dietmar Eggemann wrote:
>> On 31/03/2022 15:21, Phil Auld wrote:
>>> On Thu, Mar 31, 2022 at 11:04:31AM +0200 Dietmar Eggemann wrote:
>>>> On 30/03/2022 17:56, Phil Auld wrote:
[...]
>> 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.
prev parent reply other threads:[~2022-03-31 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 15:56 Phil Auld
2022-03-31 9:04 ` Dietmar Eggemann
2022-03-31 13:21 ` Phil Auld
2022-03-31 14:37 ` Dietmar Eggemann
2022-03-31 14:53 ` Phil Auld
2022-03-31 15:49 ` Dietmar Eggemann [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=887fd1ba-c83f-77e4-74a9-53eef1dacc49@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®