Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp390453pxu; Fri, 23 Oct 2020 03:42:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx8KOnheo1Ex6m7L6CDCADYdaAqGUX20lhmkitSYjOsvRa2e7dMgjEPhg+mZACGm7yZTa92 X-Received: by 2002:a17:906:c315:: with SMTP id s21mr1257435ejz.312.1603449762105; Fri, 23 Oct 2020 03:42:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603449762; cv=none; d=google.com; s=arc-20160816; b=e7N+nQ28Nf5lSKRUGvlMhJ2zjvteoujFgJFJAjJhrAgVly5vI4y+l6K8m4pURfnMta k0q6cBLTPRYpLirFs/I9xPkBN6msS8hBst1OmUVqgc+kY8GEZWH9vswd0xPny+es//qw JGkoQYv5Qbaa2gOzyF3+f3mBWV42VcE0FNCEiAuvEg1/BMv/NKukpWOOkejKly213Flo gX6ii3L7sdulSD1cpsIuA1+gR5GfwsEy89f1vJZsX9/jR9G43Q+JAS9ozlACywfM4giz 8zu/pxig1gcZ8LCmVwD3a0uCcDB6SI7OZ7bLo1FvAOoP41Psy0ZvbWlgLoPFBXqi35bL GeRA== 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=gmyQfJ16DOieGFXOvZtt1mm2RmCUG93kapRVx53gDLU=; b=SSmGlWh/FeGUPo25+nf2tvTsR4YGGNvXlcrnefjIJSaTCeyhPgrg8DU/5k+wPs2Shu mpkLkVCyzpFUw5oqjgsjDYyuvNV0qYFnavu8vA/NAUZ+TWJFuPr+R480YgXmh5fUzVsY OLk6M9cqOtXoPPTc9EdNLHlOhtv7PUZ32+/6XtfYR4CCs3PHLZZweWh14z4JXH0rCxMF WfvTnLmi0rv6AvuoQIk8AbaC5BE9nfyf3pq5Mqe/9/A2uct/q9VkXquJnXdYIp8k8yx8 gkgyM2XKkEJp4xtsfZa8Mg13zZylTOFEvoRKExiJJa1UEHcaU9tOrf0DvxCo5T1Y4pDt EStg== 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 rh15si542548ejb.496.2020.10.23.03.42.19; Fri, 23 Oct 2020 03:42:42 -0700 (PDT) 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 S462453AbgJWKk6 (ORCPT + 99 others); Fri, 23 Oct 2020 06:40:58 -0400 Received: from foss.arm.com ([217.140.110.172]:49004 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S370776AbgJWKk5 (ORCPT ); Fri, 23 Oct 2020 06:40:57 -0400 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 1B976113E; Fri, 23 Oct 2020 03:40:57 -0700 (PDT) Received: from [10.57.13.45] (unknown [10.57.13.45]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 5ED773F66E; Fri, 23 Oct 2020 03:40:55 -0700 (PDT) Subject: Re: [PATCH v3] coresight: etm4x: Modify core-commit of cpu to avoid the overflow of HiSilicon ETM To: Qi Liu , mathieu.poirier@linaro.org, Al.Grant@arm.com, mike.leach@linaro.org Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com References: <1603448595-22615-1-git-send-email-liuqi115@huawei.com> From: Suzuki Poulose Message-ID: Date: Fri, 23 Oct 2020 11:40:54 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 MIME-Version: 1.0 In-Reply-To: <1603448595-22615-1-git-send-email-liuqi115@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/23/20 11:23 AM, 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. > > drivers/hwtracing/coresight/Kconfig | 18 ++++++++ > drivers/hwtracing/coresight/coresight-etm4x-core.c | 50 ++++++++++++++++++++++ > 2 files changed, 68 insertions(+) > > diff --git a/drivers/hwtracing/coresight/Kconfig b/drivers/hwtracing/coresight/Kconfig > index c119824..9665d70 100644 > --- a/drivers/hwtracing/coresight/Kconfig > +++ b/drivers/hwtracing/coresight/Kconfig > @@ -110,6 +110,24 @@ 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 ETM4X_IMPDEF_HISILICON > + bool "Control overflow impdef support in HiSilicon ETM 4.x driver " > + depends on ETM4X_IMPDEF_FEATURE > + help > + This control provides overflow implement define for HiSilicon > + ETM 4.x tracer module of Hip08 platform. Overflow within ETM > + tracer module and its cpu core can be avoided by reducing core > + commit manually. > + > 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..35f4333 100644 > --- a/drivers/hwtracing/coresight/coresight-etm4x-core.c > +++ b/drivers/hwtracing/coresight/coresight-etm4x-core.c > @@ -103,12 +103,61 @@ struct etm4_enable_arg { > int rc; > }; > > +#ifdef CONFIG_ETM4X_IMPDEF_FEATURE > + > +#ifdef CONFIG_ETM4X_IMPDEF_HISILICON > + > +#define HISI_HIP08_CORE_COMMIT_CLEAR 0x3000 > +#define HISI_HIP08_CORE_COMMIT_SHIFT 12 > +static void etm4_hisi_config_core_commit(int flag) nit: s/int flag/bool enable ? > +{ > + u64 val; > + > + asm volatile("mrs %0,s3_1_c15_c2_5" : "=r"(val)); > + val &= ~HISI_HIP08_CORE_COMMIT_CLEAR; > + val |= flag << HISI_HIP08_CORE_COMMIT_SHIFT; > + asm volatile("msr s3_1_c15_c2_5,%0" : : "r"(val)); Sorry for missing this out. We don't encourage the above encodings as it will break on legacy toolchain. So, please could you follow what we do normally, by using sys_reg() macros to define the encoding and use read/write_sysreg_s() instead. See arch/arm64/include/asm/sysreg.h > +} > +#else > +static void etm4_hisi_config_core_commit(int flag) > +{ > +} > +#endif /* CONFIG_ETM4X_IMPDEF_HISILICON */ > + > +static void etm4_enable_arch_specific(void) > +{ > + /* > + * If ETM device is HiSilicon ETM device, reduce the > + * core-commit to avoid ETM overflow. > + */ > + etm4_hisi_config_core_commit(1); > +} > + > +static void etm4_disable_arch_specific(void) > +{ > + /* > + * If ETM device is HiSilicon ETM device, resume the > + * core-commit after ETM trace is complete. > + */ > + etm4_hisi_config_core_commit(0); > +} > +#else > +static void etm4_enable_arch_specific(void) > +{ > +} > + > +static void etm4_disable_arch_specific(void) > +{ > +} > +#endif /* CONFIG_ETM4X_IMPDEF_FEATURE */ > + > static int etm4_enable_hw(struct etmv4_drvdata *drvdata) > { > int i, rc; > struct etmv4_config *config = &drvdata->config; > struct device *etm_dev = &drvdata->csdev->dev; > > + etm4_enable_arch_specific(); > CS_UNLOCK(drvdata->base); Please could we move the enable_arch_specific() after the CS_UNLOCK ? That way any potential code could do something with the ETM4x registers. > > etm4_os_unlock(drvdata); > @@ -475,6 +524,7 @@ static void etm4_disable_hw(void *info) > struct device *etm_dev = &drvdata->csdev->dev; > int i; > > + etm4_disable_arch_specific(); > CS_UNLOCK(drvdata->base); > Same here Suzuki