| Message ID | 1571046986-231263-1-git-send-email-john.garry@huawei.com (mailing list archive) |
|---|---|
| Headers | show
Return-Path: <SRS0=yGTZ=YH=vger.kernel.org=linux-acpi-owner@kernel.org>
Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org
[172.30.200.123])
by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 5063417D4
for <patchwork-linux-acpi@patchwork.kernel.org>;
Mon, 14 Oct 2019 10:00:04 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
by mail.kernel.org (Postfix) with ESMTP id 33037217F9
for <patchwork-linux-acpi@patchwork.kernel.org>;
Mon, 14 Oct 2019 10:00:04 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S1731242AbfJNJ7y (ORCPT
<rfc822;patchwork-linux-acpi@patchwork.kernel.org>);
Mon, 14 Oct 2019 05:59:54 -0400
Received: from szxga05-in.huawei.com ([45.249.212.191]:3748 "EHLO huawei.com"
rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
id S1731107AbfJNJ7x (ORCPT <rfc822;linux-acpi@vger.kernel.org>);
Mon, 14 Oct 2019 05:59:53 -0400
Received: from DGGEMS403-HUB.china.huawei.com (unknown [172.30.72.58])
by Forcepoint Email with ESMTP id 0A314F38F338664DE634;
Mon, 14 Oct 2019 17:59:51 +0800 (CST)
Received: from localhost.localdomain (10.67.212.75) by
DGGEMS403-HUB.china.huawei.com (10.3.19.203) with Microsoft SMTP Server id
14.3.439.0; Mon, 14 Oct 2019 17:59:42 +0800
From: John Garry <john.garry@huawei.com>
To: <stable@vger.kernel.org>
CC: <catalin.marinas@arm.com>, <will@kernel.org>, <rjw@rjwysocki.net>,
<lenb@kernel.org>, <robert.moore@intel.com>,
<erik.schmauss@intel.com>, <sudeep.holla@arm.com>,
<rrichter@marvell.com>, <jeremy.linton@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>,
<linuxarm@huawei.com>, <gregkh@linuxfoundation.org>,
<guohanjun@huawei.com>, <wanghuiqiang@huawei.com>,
John Garry <john.garry@huawei.com>
Subject: [PATCH for-stable-4.19 0/3] ACPI,
arm64: Backport for ACPI PPTT 6.3 thread flag
Date: Mon, 14 Oct 2019 17:56:23 +0800
Message-ID: <1571046986-231263-1-git-send-email-john.garry@huawei.com>
X-Mailer: git-send-email 2.8.1
MIME-Version: 1.0
Content-Type: text/plain
X-Originating-IP: [10.67.212.75]
X-CFilter-Loop: Reflected
Sender: linux-acpi-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-acpi.vger.kernel.org>
X-Mailing-List: linux-acpi@vger.kernel.org
|
| Series |
ACPI, arm64: Backport for ACPI PPTT 6.3 thread flag
|
expand
|
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: https://lkml.org/lkml/2019/10/10/724 Erik Schmauss (1): ACPICA: ACPI 6.3: PPTT add additional fields in Processor Structure Flags 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/acpi/actbl2.h | 7 +++-- include/linux/acpi.h | 5 ++++ 4 files changed, 77 insertions(+), 6 deletions(-)