Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp2315720pxu; Mon, 7 Dec 2020 03:30:11 -0800 (PST) X-Google-Smtp-Source: ABdhPJyuYoZ9TGeTfLc1GApjVIl4bmb49AETCqE+hO+/ESRLYiljPtuGRqLzcd8f2KQxC0NDQF7X X-Received: by 2002:a05:6402:21c7:: with SMTP id bi7mr20137213edb.54.1607340610786; Mon, 07 Dec 2020 03:30:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607340610; cv=none; d=google.com; s=arc-20160816; b=McwGvwU84/d/YDxi10bngx05bmrkeiaFQXCfdjBTf37RaGjfFfEI9TqFEwO2+yO8Uu O5nHe9gvFPKnNLfWBzkHkKWro7llRN8XUKBTURMDh0en3+FwTzWpgdn78Ke9JHsI73ip LFePqSDqogSQJinKitmZQ7jkWYpmLPWk9N6OJDkZKLI4JPe6al+W0BMroQeC5dC4YZd3 PI0uj++PJOJmV9f+2++blyTrnzeOelEhMSMMG7DBSHx5ZZKsEJjdFB6fUFYI+ewFgKJx hxpkakMeYlfxKiyv/+xC042NMro9pRv/GzXe0R9RXrZ1BFMZtwtd1YRV5sjZVIAYsUNM 2p4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=2ONo9HSGB15tOmvPZAKpymKFZRVc4xERzghHdZgGoec=; b=E3eA4VKqO4nTErjHSlv6rk26RJCQGtQOInKKGmfcM8mmrqCAShbk6qa+K4+1dr016j vyrSaMrzG+qtIoJHS+6bo/jn351a+dhjesCepA25g3VR4QJPWrK5BEUQMb/PlmieqtMO pUPSFYNvZv4v+IMI3K21+ysbbfymMUO81pqpzXV87spR9S9zCs2+J2Ca7j5I2Upti/kI iP38thMAxumurAegPnkTnFcY29eu67rP1DNx+SpEBzFelOx39w54y1WhsZgfKRjjbkJH rHbUsoGI8WXC/g0sdmHVowo05G1Vsr/IkNwFX7Qe9zdyQZLDpliYz/81BolUvNPAul4Q JZXg== 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 r24si6318715eji.211.2020.12.07.03.29.48; Mon, 07 Dec 2020 03:30:10 -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 S1726370AbgLGL2H (ORCPT + 99 others); Mon, 7 Dec 2020 06:28:07 -0500 Received: from foss.arm.com ([217.140.110.172]:47794 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726188AbgLGL2G (ORCPT ); Mon, 7 Dec 2020 06:28:06 -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 CFF531042; Mon, 7 Dec 2020 03:27:20 -0800 (PST) Received: from [10.57.63.221] (unknown [10.57.63.221]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 480A43F66B; Mon, 7 Dec 2020 03:27:19 -0800 (PST) Subject: Re: [PATCH v5] coresight: etm4x: Modify core-commit of cpu to avoid the overflow of HiSilicon ETM To: Qi Liu , Mathieu Poirier Cc: mike.leach@linaro.org, coresight@lists.linaro.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com 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> <0e56f56e-157e-ecf2-bb21-74b79ffdf2ac@huawei.com> From: Suzuki K Poulose Message-ID: Date: Mon, 7 Dec 2020 11:27:16 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1 MIME-Version: 1.0 In-Reply-To: <0e56f56e-157e-ecf2-bb21-74b79ffdf2ac@huawei.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/7/20 11:21 AM, Qi Liu wrote: > > 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); I would do : // Rename the HISI_HIP08_CORE_COMMIT_CLEAR to HISI_HIP08_CORE_COMMIT_MASK // above. #define HISI_HIP08_CORE_COMMIT_MASK 0x3000 #define HISI_HIP08_CORE_COMMIT_FULL 0b00 #define HISI_HIP08_CORE_COMMIT_LVL_1 0b01 u8 commit = enable ? HISI_HIP08_CORE_COMMIT_LVL_1 : HISI_HIP08_CORE_COMMIT_FULL; ... val |= commit << HISI_HIP08_CORE_COMMIT_SHIFT; .. Suzuki