Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp270764ybp; Thu, 10 Oct 2019 17:54:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqx69/tAQAHsV30siF6k6A3ryubvKYx7Ucyc8MtjRAg+3S1+NFR0S+a1K4VU9Fm/QTdhtV+L X-Received: by 2002:a05:6402:698:: with SMTP id f24mr11085718edy.172.1570755286655; Thu, 10 Oct 2019 17:54:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570755286; cv=none; d=google.com; s=arc-20160816; b=jGhwaJdYPGU8IqtX3ImNxcWYJRYEgOuUvttSzeYoUpyf67Roqj9DxQMpUZr1GrJPav cwV9QLSYQree9FePu0CkeNF3kaBV3e+xq42UxOPbgcPcgQXSLZZO8s07jxzNVraWyTmo rLhjWGoPQFobHLRERIw6AK+i2mwFRWQ0zGN54cKDJt9ftGf9NZ+4ROhf4VHiSmPrKwuX kCz3mWyHBPctGQkMUwM+TupB3Q5w4vCuUfSvsRZxvGB1700hBdsxZBHTFr6S4s83N3zP S22djHHq+1z3uHzVURruPj77AGsVlpmi4KaRV8ON6sesb+3sR4FuSqnLX6DKABbtKK8p LbOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=cIGzEs6J9pZl2uYYmKf8AdNQIv7CMTgyjsuX5QQTIyk=; b=U4LCOY9kRXfrQg/sR7y9S6KeJiLmxQ4AOu70OLfsXQ0HYBH323aCNTDY4x2J3AxCDP qck6RV+4KVkqzdDnQMbrJi9Kx0qHf8qd+z4ajrU6LCv4gucOGLAVKFEzClKs8YR2YaeS 59no0/zFDLqUfqRAdgi8JPVGf2dfJsSRK7Ob6Fi3lUM7Nen+Wod7Nep3nvSZJPd6wapf RzVojW4zen1ckMOuJrQgYTEybbFAOGIpaWX1PpbD8HKwjcezZD5evVE96xMxRizv02kL W75xdkFhV9HIPhpBcOOelXkI23sCdwF98ZFfLJctm4tx6gYdU+uaMP1ULqDSfmM9JpbU ZyKw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id nj7si4151758ejb.262.2019.10.10.17.54.23; Thu, 10 Oct 2019 17:54:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727882AbfJKAyA (ORCPT + 99 others); Thu, 10 Oct 2019 20:54:00 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:3728 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727518AbfJKAx7 (ORCPT ); Thu, 10 Oct 2019 20:53:59 -0400 Received: from DGGEMS405-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id DAD81C24DE4D932AB452; Fri, 11 Oct 2019 08:53:57 +0800 (CST) Received: from [127.0.0.1] (10.177.223.23) by DGGEMS405-HUB.china.huawei.com (10.3.19.205) with Microsoft SMTP Server id 14.3.439.0; Fri, 11 Oct 2019 08:53:50 +0800 Subject: Re: [RFC PATCH 0/3] ACPI, arm64: Backport for ACPI PPTT 6.3 thread flag for stable 4.19.x To: John Garry , , , , , , , , , CC: , , , , , References: <1570714192-236724-1-git-send-email-john.garry@huawei.com> From: Hanjun Guo Message-ID: Date: Fri, 11 Oct 2019 08:53:32 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <1570714192-236724-1-git-send-email-john.garry@huawei.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.223.23] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John, On 2019/10/10 21:29, John Garry wrote: > 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. Thanks for doing this, and this patch set fix my CPU topology issue in 4.19 kernel with updated firmware. > > Note: I'm sending this as an RFC before sending to stable proper. I also > have a 5.2 and 5.3 backport which are almost the same, and only > significant change being that the ACPICA patch is not required. 5.2 stable was end of life, so only 4.19 and 5.3 are needed I think. Thanks Hanjun