Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2313127pxu; Mon, 7 Dec 2020 03:25:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJxKCGcMp8Vcm8auji+A261Gyzh8s3JjaQv9akAJ3cL57JwOqcPlPmljseCtAFrQsT1cajjY X-Received: by 2002:a17:906:1752:: with SMTP id d18mr18766844eje.529.1607340306266; Mon, 07 Dec 2020 03:25:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607340306; cv=none; d=google.com; s=arc-20160816; b=xRvyp+2+cFLQNiXPpD7gRU4+laFm7VcqR04u8cH1LUOk72YX4cL/BYpG8SqHG04TN5 aLGtqExwBwnuHW76CQ/CfQ14TY1Qyz+2UEARQjybuNkiFN/9jc8Srea0nyDEkFxOuWav j6FHSCCnXiZUBgoYAUES7LezmaqCuxFb3BWjIz8MUfcLjfMEVi7D+8UKFVJsdcyZFCgL ZkFrk/iwdLMBYtNArmMimzIIY2nYQPzSEpkxHj3jYJfkX44Ro982MZPgDCFXw2DprwqS pjFmtlDuYU1Z57vx5zmDYQs9UwgSsIVuuTGgdWBLJcGejpcckQH0KTwb0zhbCM4pkfun CIKw== 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 :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=uN1TvVFbf4qXIl6/AmtG+XGfGV6qXmr0mjHvo0e7vM0=; b=CRKiEEOGutpfncstTXCe9CPxSoRqnW4aOJ9EX1ItbWicWjugRs5pDSTQDSTXpJZCpb KPxxIsY+2OTOXxZXV/47lgTNJh/XWrvEzrmTHg1VrzKYcsDu5vJqCU+1dblSPSVhPcYL utGcMffuWBzunOsJkaHtzdZbhUV0K8vPMpkECkcF3GybklnKu8W1XJErViLsSiYQqD+k ep4Z2YDt7DOYo9VczUOZyNJXXI5FHc8ByLpT+DH35Iegw2N6fKO4uBbOecddRT5slayR 8nnlr8HEg04t6RPvV8Fn1HK3HaIku+nwRkAxGoTbF/lJ1KcrBcGbWG6zgmEhFwTrHybc m9jA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l19si1777677eja.479.2020.12.07.03.24.42; Mon, 07 Dec 2020 03:25:06 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726677AbgLGLWV (ORCPT + 99 others); Mon, 7 Dec 2020 06:22:21 -0500 Received: from szxga06-in.huawei.com ([45.249.212.32]:8961 "EHLO szxga06-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726322AbgLGLWU (ORCPT ); Mon, 7 Dec 2020 06:22:20 -0500 Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.60]) by szxga06-in.huawei.com (SkyGuard) with ESMTP id 4CqLV24sdGzhmZ7; Mon, 7 Dec 2020 19:21:14 +0800 (CST) Received: from [127.0.0.1] (10.65.95.32) by DGGEMS407-HUB.china.huawei.com (10.3.19.207) with Microsoft SMTP Server id 14.3.487.0; Mon, 7 Dec 2020 19:21:30 +0800 Subject: Re: [PATCH v5] coresight: etm4x: Modify core-commit of cpu to avoid the overflow of HiSilicon ETM To: Suzuki K Poulose , Mathieu Poirier References: <1606397670-15657-1-git-send-email-liuqi115@huawei.com> <20201204185551.GB1424711@xps15> <448eb009-da3e-b918-984d-cf563a64f31d@huawei.com> <07243eef-dbcf-6500-a66b-5c0e1689ece9@arm.com> CC: , , , , From: Qi Liu Message-ID: <0e56f56e-157e-ecf2-bb21-74b79ffdf2ac@huawei.com> Date: Mon, 7 Dec 2020 19:21:30 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <07243eef-dbcf-6500-a66b-5c0e1689ece9@arm.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.65.95.32] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Suzuki, On 2020/12/7 18:38, Suzuki K Poulose wrote: > On 12/7/20 2:08 AM, Qi Liu wrote: >> Hi Mathieu, >> >> On 2020/12/5 2:55, Mathieu Poirier wrote: >>> On Thu, Nov 26, 2020 at 09:34:30PM +0800, Qi Liu wrote: >>>> The ETM device can't keep up with the core pipeline when cpu core >>>> is at full speed. This may cause overflow within core and its ETM. >>>> This is a common phenomenon on ETM devices. >>>> >>>> On HiSilicon Hip08 platform, a specific feature is added to set >>>> core pipeline. So commit rate can be reduced manually to avoid ETM >>>> overflow. >>>> >>>> Signed-off-by: Qi Liu >>>> --- >>>> Change since v1: >>>> - add CONFIG_ETM4X_IMPDEF_FEATURE and CONFIG_ETM4X_IMPDEF_HISILICON >>>> to keep specific feature off platforms which don't use it. >>>> Change since v2: >>>> - remove some unused variable. >>>> Change since v3: >>>> - use read/write_sysreg_s() to access register. >>>> Change since v4: >>>> - rename the call back function to a more generic name, and fix some >>>> compile warnings. >>>> >>>> drivers/hwtracing/coresight/Kconfig | 9 +++ >>>> drivers/hwtracing/coresight/coresight-etm4x-core.c | 88 ++++++++++++++++++++++ >>>> drivers/hwtracing/coresight/coresight-etm4x.h | 8 ++ >>>> 3 files changed, 105 insertions(+) >>>> >>>> diff --git a/drivers/hwtracing/coresight/Kconfig b/drivers/hwtracing/coresight/Kconfig >>>> index c119824..1cc3601 100644 >>>> --- a/drivers/hwtracing/coresight/Kconfig >>>> +++ b/drivers/hwtracing/coresight/Kconfig >>>> @@ -110,6 +110,15 @@ config CORESIGHT_SOURCE_ETM4X >>>> To compile this driver as a module, choose M here: the >>>> module will be called coresight-etm4x. >>>> >>>> +config ETM4X_IMPDEF_FEATURE >>>> + bool "Control overflow impdef support in CoreSight ETM 4.x driver " >>>> + depends on CORESIGHT_SOURCE_ETM4X >>>> + help >>>> + This control provides overflow implement define for CoreSight >>>> + ETM 4.x tracer module which could not reduce commit race >>>> + automatically, and could avoid overflow within ETM tracer module >>>> + and its cpu core. >>>> + >>>> config CORESIGHT_STM >>>> tristate "CoreSight System Trace Macrocell driver" >>>> depends on (ARM && !(CPU_32v3 || CPU_32v4 || CPU_32v4T)) || ARM64 >>>> diff --git a/drivers/hwtracing/coresight/coresight-etm4x-core.c b/drivers/hwtracing/coresight/coresight-etm4x-core.c >>>> index abd706b..fcee27a 100644 >>>> --- a/drivers/hwtracing/coresight/coresight-etm4x-core.c >>>> +++ b/drivers/hwtracing/coresight/coresight-etm4x-core.c >>>> @@ -3,6 +3,7 @@ >>>> * Copyright (c) 2014, The Linux Foundation. All rights reserved. >>>> */ >>>> >>>> +#include >>>> #include >>>> #include >>>> #include >>>> @@ -28,7 +29,9 @@ >>>> #include >>>> #include >>>> #include >>>> + >>>> #include >>>> +#include >>>> #include >>>> #include >>>> >>>> @@ -103,6 +106,87 @@ struct etm4_enable_arg { >>>> int rc; >>>> }; >>>> >>>> +#ifdef CONFIG_ETM4X_IMPDEF_FEATURE >>>> + >>>> +#define HISI_HIP08_AMBA_ID 0x000b6d01 >>>> +#define ETM4_AMBA_MASK 0xfffff >>>> +#define HISI_HIP08_CORE_COMMIT_CLEAR 0x3000 >>> >>> Here bit 12 and 13 are cleared but in etm4_hisi_config_core_commit() only bit 12 >>> is set - is this intentional? What is bit 13 for? >>> >> bit 12 and 13 are used together to set core-commit, 2'b00 means cpu is at full speed, >> 2'b01, 2'b10, 2'b11 means reduce the speed of cpu pipeline, and 2'b01 means speed is >> reduced to minimum value. So bit 12 and 13 should be cleared together in >> etm4_hisi_config_core_commit(). > > Please could you document this in the function. > of course, thanks. >> >> Qi >> >>>> +#define HISI_HIP08_CORE_COMMIT_SHIFT 12 >>>> +#define HISI_HIP08_CORE_COMMIT_REG sys_reg(3, 1, 15, 2, 5) >>>> + >>>> +struct etm4_arch_features { >>>> + void (*arch_callback)(bool enable); >>>> +}; >>>> + >>>> +static bool etm4_hisi_match_pid(unsigned int id) >>>> +{ >>>> + return (id & ETM4_AMBA_MASK) == HISI_HIP08_AMBA_ID; >>>> +} >>>> + >>>> +static void etm4_hisi_config_core_commit(bool enable) >>>> +{ >>>> + u64 val; >>>> + >>>> + val = read_sysreg_s(HISI_HIP08_CORE_COMMIT_REG); >>>> + val &= ~HISI_HIP08_CORE_COMMIT_CLEAR; >>>> + val |= enable << HISI_HIP08_CORE_COMMIT_SHIFT; > > I would use the explicitly masked values when you update > a register. > ok, how about changing these code to this: val &= ~GENMASK(12, 13); Thanks Qi > With the above: > > Reviewed-by: Suzuki K Poulose > > . >