From: John Garry <john.garry@huawei•com>
To: <stable@vger•kernel.org>
Cc: John Garry <john.garry@huawei•com>,
gregkh@linuxfoundation•org, catalin.marinas@arm•com,
guohanjun@huawei•com, rjw@rjwysocki•net,
linux-kernel@vger•kernel.org, jeremy.linton@arm•com,
linuxarm@huawei•com, linux-acpi@vger•kernel.org,
rrichter@marvell•com, wanghuiqiang@huawei•com,
sudeep.holla@arm•com, will@kernel•org,
linux-arm-kernel@lists•infradead.org, lenb@kernel•org
Subject: [PATCH for-stable-5.3 0/3] ACPI, arm64: Backport for ACPI PPTT 6.3 thread flag
Date: Mon, 14 Oct 2019 19:56:00 +0800 [thread overview]
Message-ID: <1571054162-71090-1-git-send-email-john.garry@huawei.com> (raw)
This series is a backport of the ACPI PPTT 6.3 thread flag feature for
supporting arm64 systems.
The background is that some arm64 implementations are broken, in that they
incorrectly advertise that a CPU is mutli-threaded, when it is not - the
HiSilicon Taishanv110 rev 2, aka tsv110, being an example.
This leads to the system topology being incorrect. The reason being that
arm64 topology code uses a combination of ACPI PPTT (Processor Properties
Topology Table) and the system MPIDR (Multiprocessor Affinity Register) MT
bit to determine the topology.
Until ACPI 6.3, the PPTT did not have any method to determine whether
a CPU was multi-threaded, so only the MT bit is used - hence the
broken topology for some systems.
In ACPI 6.3, a PPTT thread flag was introduced, which - when supported -
would be used by the kernel to determine really if a CPU is multi-threaded
or not, so that we don't get incorrect topology.
RFC originally sent for 4.19: https://lkml.org/lkml/2019/10/10/724
Jeremy Linton (2):
ACPI/PPTT: Add support for ACPI 6.3 thread flag
arm64: topology: Use PPTT to determine if PE is a thread
arch/arm64/kernel/topology.c | 19 ++++++++++---
drivers/acpi/pptt.c | 52 ++++++++++++++++++++++++++++++++++++
include/linux/acpi.h | 5 ++++
3 files changed, 72 insertions(+), 4 deletions(-)
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-10-14 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 11:56 John Garry [this message]
2019-10-14 11:56 ` [PATCH for-stable-5.3 1/2] ACPI/PPTT: Add support for ACPI 6.3 thread flag John Garry
2019-10-14 23:29 ` Sasha Levin
2019-10-15 8:16 ` John Garry
2019-10-15 22:04 ` Sasha Levin
2019-10-14 11:56 ` [PATCH for-stable-5.3 2/2] arm64: topology: Use PPTT to determine if PE is a thread John Garry
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=1571054162-71090-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=guohanjun@huawei$(echo .)com \
--cc=jeremy.linton@arm$(echo .)com \
--cc=lenb@kernel$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxarm@huawei$(echo .)com \
--cc=rjw@rjwysocki$(echo .)net \
--cc=rrichter@marvell$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
--cc=sudeep.holla@arm$(echo .)com \
--cc=wanghuiqiang@huawei$(echo .)com \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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