From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] arm64: topology: add MPIDR-based detection
Date: Thu, 10 Jul 2014 12:03:18 +0100 [thread overview]
Message-ID: <20140710110318.GA10749@arm.com> (raw)
In-Reply-To: <1402102527-10569-1-git-send-email-zlim@broadcom.com>
On Sat, Jun 07, 2014 at 01:55:27AM +0100, Zi Shen Lim wrote:
> Lorenzo and Mark agreed on the following updated patch from Lorenzo:
> http://www.spinics.net/lists/arm-kernel/msg336998.html
>
> W.r.t. cluster numbering, we're now back to where we were with the
> the original patch sent out in April:
> https://lkml.org/lkml/2014/4/22/951
>
> Were there any other objections to this approach?
> AFAICT, this patch should be good to go for 3.16.
> ------->8--------
>
> Create cpu topology based on MPIDR. When hardware sets MPIDR to sane
> values, this method will always work. Therefore it should also work well
> as the fallback method. [1]
>
> When we have multiple processing elements in the system, we create
> the cpu topology by mapping each affinity level (from lowest to highest)
> to threads (if they exist), cores, and clusters.
>
> [1] http://www.spinics.net/lists/arm-kernel/msg317445.html
>
> Acked-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Signed-off-by: Zi Shen Lim <zlim@broadcom.com>
> Signed-off-by: Mark Brown <broonie@linaro.org>
> ---
> arch/arm64/include/asm/cputype.h | 2 ++
> arch/arm64/kernel/topology.c | 47 ++++++++++++++++++++++++++++------------
> 2 files changed, 35 insertions(+), 14 deletions(-)
Applied for 3.17. Thanks.
--
Catalin
prev parent reply other threads:[~2014-07-10 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-07 0:55 [RESEND PATCH] arm64: topology: add MPIDR-based detection Zi Shen Lim
2014-07-10 11:03 ` Catalin Marinas [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=20140710110318.GA10749@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).