mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org, Phil Auld <pauld@redhat.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] arch/arm64: Fix topology initialization for core scheduling
Date: Mon,  4 Apr 2022 11:10:48 +0100	[thread overview]
Message-ID: <164906426317.23108.12415745228600027656.b4-ty@kernel.org> (raw)
In-Reply-To: <20220331153926.25742-1-pauld@redhat.com>

On Thu, 31 Mar 2022 11:39:26 -0400, Phil Auld wrote:
> Arm64 systems rely on store_cpu_topology() to call update_siblings_masks()
> to transfer the toplogy to the various cpu masks. This needs to be done
> before the call to notify_cpu_starting() which tells the scheduler about
> each cpu found, otherwise the core scheduling data structures are setup
> in a way that does not match the actual topology.
> 
> With smt_mask not setup correctly we bail on `cpumask_weight(smt_mask) == 1`
> for !leaders in:
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arch/arm64: Fix topology initialization for core scheduling
      https://git.kernel.org/arm64/c/5524cbb1bfcd

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev

  reply	other threads:[~2022-04-04 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 15:39 Phil Auld
2022-04-04 10:10 ` Will Deacon [this message]
2022-04-04 14:26   ` Phil Auld

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=164906426317.23108.12415745228600027656.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=kernel-team@android.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 \
    /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®