From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Valentin Schneider <valentin.schneider@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Zengtao (B)" <prime.zeng@hisilicon.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Jeremy Linton <Jeremy.Linton@arm.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>
Subject: Re: [PATCH] arm64: topology: Stop using MPIDR for topology information
Date: Mon, 7 Sep 2020 22:35:35 +0100 [thread overview]
Message-ID: <159951413581.3126645.5011278165801551941.b4-ty@kernel.org> (raw)
In-Reply-To: <20200829130016.26106-1-valentin.schneider@arm.com>
On Sat, 29 Aug 2020 14:00:16 +0100, Valentin Schneider wrote:
> In the absence of ACPI or DT topology data, we fallback to haphazardly
> decoding *something* out of MPIDR. Sadly, the contents of that register are
> mostly unusable due to the implementation leniancy and things like Aff0
> having to be capped to 15 (despite being encoded on 8 bits).
>
> Consider a simple system with a single package of 32 cores, all under the
> same LLC. We ought to be shoving them in the same core_sibling mask, but
> MPIDR is going to look like:
>
> [...]
Applied to arm64 (for-next/topology), thanks!
[1/1] arm64: topology: Stop using MPIDR for topology information
https://git.kernel.org/arm64/c/3102bc0e6ac7
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Valentin Schneider <valentin.schneider@arm.com>
Cc: Will Deacon <will@kernel.org>,
catalin.marinas@arm.com, Robin Murphy <robin.murphy@arm.com>,
Jeremy Linton <Jeremy.Linton@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
"Zengtao \(B\)" <prime.zeng@hisilicon.com>,
Sudeep Holla <sudeep.holla@arm.com>,
kernel-team@android.com,
Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [PATCH] arm64: topology: Stop using MPIDR for topology information
Date: Mon, 7 Sep 2020 22:35:35 +0100 [thread overview]
Message-ID: <159951413581.3126645.5011278165801551941.b4-ty@kernel.org> (raw)
In-Reply-To: <20200829130016.26106-1-valentin.schneider@arm.com>
On Sat, 29 Aug 2020 14:00:16 +0100, Valentin Schneider wrote:
> In the absence of ACPI or DT topology data, we fallback to haphazardly
> decoding *something* out of MPIDR. Sadly, the contents of that register are
> mostly unusable due to the implementation leniancy and things like Aff0
> having to be capped to 15 (despite being encoded on 8 bits).
>
> Consider a simple system with a single package of 32 cores, all under the
> same LLC. We ought to be shoving them in the same core_sibling mask, but
> MPIDR is going to look like:
>
> [...]
Applied to arm64 (for-next/topology), thanks!
[1/1] arm64: topology: Stop using MPIDR for topology information
https://git.kernel.org/arm64/c/3102bc0e6ac7
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-07 21:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 13:00 [PATCH] arm64: topology: Stop using MPIDR for topology information Valentin Schneider
2020-08-29 13:00 ` Valentin Schneider
2020-09-02 3:24 ` Zengtao (B)
2020-09-02 3:24 ` Zengtao (B)
2020-09-02 10:50 ` Sudeep Holla
2020-09-02 10:50 ` Sudeep Holla
2020-09-02 10:52 ` Valentin Schneider
2020-09-02 10:52 ` Valentin Schneider
2020-09-03 1:44 ` Zengtao (B)
2020-09-03 1:44 ` Zengtao (B)
2020-09-09 11:21 ` Valentin Schneider
2020-09-09 11:21 ` Valentin Schneider
2020-09-02 10:04 ` Sudeep Holla
2020-09-02 10:04 ` Sudeep Holla
2020-09-02 10:52 ` Valentin Schneider
2020-09-02 10:52 ` Valentin Schneider
2020-09-07 21:35 ` Will Deacon [this message]
2020-09-07 21:35 ` Will Deacon
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=159951413581.3126645.5011278165801551941.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Jeremy.Linton@arm.com \
--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=morten.rasmussen@arm.com \
--cc=prime.zeng@hisilicon.com \
--cc=robin.murphy@arm.com \
--cc=sudeep.holla@arm.com \
--cc=valentin.schneider@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.