Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp2734816pxb; Mon, 31 Jan 2022 03:12:01 -0800 (PST) X-Google-Smtp-Source: ABdhPJzMUUMLD7Hl/1kYk8ABcC2lcBVFySm4WpopPzzeW/2TZ6ZSLbkHcP5sz8bGNs6BhU6ang/t X-Received: by 2002:a63:81c8:: with SMTP id t191mr16131374pgd.223.1643627521612; Mon, 31 Jan 2022 03:12:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643627521; cv=none; d=google.com; s=arc-20160816; b=Ni1KeyVG3Sl54cq2UL3NGVmk34wt0llIzk6ssSZyomOjABfHRBHUW/IHaYU6V3DsiH vcsS/eje5QkIt03FJ6ZFcJl8gfFK14A/6ycVkPw1+u+7TuDXHwc7ovOISsa8tbHy13up Q9HsFL1lGMXGbqx/hwJs6l9b1a8iPZT35vhiZg9X8u0RE6nc3zP5r1FQYwOTJRGVi1JH ZlEwcNOCZ8sKHA6gfnMneUxcKSVSVPvdiJXtv86fqxIrFy/hKFAR1kBzODNNb55XOeHS NjYoAWDKkPLsEhVf4+Te9mM8P0T4D4P1F581P3HFzgjOj81Hfbcs3UG4JunCl9ubmSC0 HQOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=npHUWWGSwj6GLlfnE83Rbu8cg1xSyYxnNQjxNsScNgM=; b=pN0gmqNrmM1pFlBpC5NnlwrPMSn6kEUt/V+cZET0MqgP4zCCdZk9gVelmrhem4BxGO wHcM606Pa9Z+Ff44q2aqolAEVKShY75Ct39kW/7Al0hFyeNL3epFAP8hHnpqGPLWmfOH TrGZ6OIK/aaHpy+M+GVC3kTkuVmAMMnyA0hKIYml5baiVj+tjH5ty0C/mYHQezl315YJ Qb5aWU9B4uZlUoafZAV/wnV+UHsOWLvrjUZ+qPB7bsLOeUJVsTi1RV+GpdPBTn0mRcqK mcVpie1Z6lWbyXaaOwUpWewmB9lGah/A1s2JLzYvjOSwHEB+7Kt9DZeLDWi2K41NjBiu D9NQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e19si11899508pfv.218.2022.01.31.03.11.50; Mon, 31 Jan 2022 03:12:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349527AbiA1P2e (ORCPT + 99 others); Fri, 28 Jan 2022 10:28:34 -0500 Received: from foss.arm.com ([217.140.110.172]:49664 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349368AbiA1P2a (ORCPT ); Fri, 28 Jan 2022 10:28:30 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id E6A1312FC; Fri, 28 Jan 2022 07:28:29 -0800 (PST) Received: from [10.57.68.47] (unknown [10.57.68.47]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2DB403F793; Fri, 28 Jan 2022 07:28:28 -0800 (PST) Message-ID: <136be111-c75e-48b2-caef-cbf4900b6ce1@arm.com> Date: Fri, 28 Jan 2022 15:28:23 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:91.0) Gecko/20100101 Thunderbird/91.5.1 Subject: Re: [RFC PATCH] ACPI / amba: Skip creating amba device when associated cpu is not online Content-Language: en-GB To: Suzuki K Poulose , chenxiang , linux@armlinux.org.uk, vkoul@kernel.org, linux-arm-kernel@lists.infradead.org, mathieu.poirier@linaro.org Cc: coresight@lists.linaro.org, linux-kernel@vger.kernel.org, linuxarm@huawei.com, Anshuman Khandual , Sudeep Holla References: <1641544906-7069-1-git-send-email-chenxiang66@hisilicon.com> <2f3c5e6b-7000-8fa2-21f7-3b0c3fb66ae3@arm.com> From: Robin Murphy In-Reply-To: <2f3c5e6b-7000-8fa2-21f7-3b0c3fb66ae3@arm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2022-01-28 11:00, Suzuki K Poulose wrote: > Hi Xiang > > On 07/01/2022 08:41, chenxiang wrote: >> From: Xiang Chen >> >> If not up all the cpus with command line "maxcpus=x", system will be >> blocked. >> We find that some amba devices such as ETM devices, are associated with >> special cpus, and if the cpu is not up, the register of associated device >> is not allowed to access. BIOS reports all the ETM device nodes and a >> amba device is created for every ETM device, so even if one cpu is not >> up, >> the amba device will still be created for the associated device, and also >> the register of device (pid and cid) will be accessed when adding amba >> device which will cause the issue. >> To fix it, skip creating amba device if it is associated with a cpu which >> is not online. > > I understand the issue. We do not have an issue at least on DT based > platforms with a similar environment (Juno). The key is the power > management for the components. > > There are two separate issues at play here : > > 1) Power management with ACPI. I believe there is a solution in progress > to address this. > > 2) The ETM is in the same power domain as that of the CPU and normal > device power management may not work without the CPU being online. > > 3) Additionally we have other issue of supporting system instructions > with ACPI, which do not appear on the AMBA bus. > > Considering all of these, the ideal solution is to : > > 1) Implement power management for ACPI, which is anyway in progress >   (at least for SCMI based systems) > 2) Move the ETM driver away from the AMBA framework. That would make >    the CPU online problem and the (3) above easier to solve. >    Anshuman is going to look into this. > > In the meantime, we could have this temporary fix in and solve it > forever by moving away from the AMBA. Out of curiosity, what happens when you boot with "maxcpus=" and then manually bring up the extra cpus from userspace later? Is there a chance that tracing will explode if some online CPUs have ETM initialised but others don't? Robin. >> >> Signed-off-by: Xiang Chen >> --- >>   drivers/acpi/acpi_amba.c | 36 ++++++++++++++++++++++++++++++++++++ >>   1 file changed, 36 insertions(+) >> >> diff --git a/drivers/acpi/acpi_amba.c b/drivers/acpi/acpi_amba.c >> index ab8a4e0191b1..2369198f734b 100644 >> --- a/drivers/acpi/acpi_amba.c >> +++ b/drivers/acpi/acpi_amba.c >> @@ -16,6 +16,7 @@ >>   #include >>   #include >>   #include >> +#include >>   #include "internal.h" >> @@ -45,6 +46,35 @@ static void amba_register_dummy_clk(void) >>       clk_register_clkdev(amba_dummy_clk, "apb_pclk", NULL); >>   } >> +static int acpi_handle_to_cpuid(acpi_handle handle) >> +{ >> +    int cpu = -1; >> +    struct acpi_processor *pr; >> + >> +    for_each_possible_cpu(cpu) { >> +        pr = per_cpu(processors, cpu); >> +        if (pr && pr->handle == handle) >> +            break; >> +    } >> + >> +    return cpu; >> +} >> + > > Please could we reuse the function in coresight-platform.c ? > i.e, move it to a generic location and share it, rather than > duplicating it ? > > >> +static int acpi_dev_get_cpu(struct acpi_device *adev) >> +{ >> +    acpi_handle cpu_handle; >> +    acpi_status status; >> +    int cpu; >> + >> +    status = acpi_get_parent(adev->handle, &cpu_handle); >> +    if (ACPI_FAILURE(status)) >> +        return -1; >> +    cpu = acpi_handle_to_cpuid(cpu_handle); >> +    if (cpu >= nr_cpu_ids) >> +        return -1; >> +    return cpu; >> +} >> + >>   static int amba_handler_attach(struct acpi_device *adev, >>                   const struct acpi_device_id *id) >>   { >> @@ -54,11 +84,17 @@ static int amba_handler_attach(struct acpi_device >> *adev, >>       bool address_found = false; >>       int irq_no = 0; >>       int ret; >> +    int cpu; >>       /* If the ACPI node already has a physical device attached, skip >> it. */ >>       if (adev->physical_node_count) >>           return 0; >> +    /* If the cpu associated with the device is not online, skip it. */ >> +    cpu = acpi_dev_get_cpu(adev); >> +    if (cpu >= 0 && !cpu_online(cpu)) >> +        return 0; >> + > > Except for the comment above, the patch looks good to me. > > Suzuki > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel