Linux Documentation
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	linux-arm-kernel@lists.infradead.org, suzuki.poulose@arm.com
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Mike Leach <mike.leach@linaro.org>,
	James Clark <james.clark@arm.com>, Leo Yan <leo.yan@linaro.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, coresight@lists.linaro.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 1/3] coresight: etm: Override TRCIDR3.CCITMIN on errata affected cpus
Date: Mon, 21 Aug 2023 08:04:58 +0530	[thread overview]
Message-ID: <b6b76d8e-cce5-5d79-9488-645a5420558d@arm.com> (raw)
In-Reply-To: <51f4b571-a5b2-b1bb-b990-fe2c4c5387bf@infradead.org>



On 8/19/23 02:41, Randy Dunlap wrote:
> Hi--
> 
> On 8/18/23 04:20, Anshuman Khandual wrote:
>> This work arounds errata 1490853 on Cortex-A76, and Neoverse-N1, errata
>> 1491015 on Cortex-A77, errata 1502854 on Cortex-X1, and errata 1619801 on
>> Neoverse-V1, based affected cpus, where software read for TRCIDR3.CCITMIN
>> field in ETM gets an wrong value.
>>
>> If software uses the value returned by the TRCIDR3.CCITMIN register field,
>> then it will limit the range which could be used for programming the ETM.
>> In reality, the ETM could be programmed with a much smaller value than what
>> is indicated by the TRCIDR3.CCITMIN field and still function correctly.
>>
>> If software reads the TRCIDR3.CCITMIN register field, corresponding to the
>> instruction trace counting minimum threshold, observe the value 0x100 or a
>> minimum cycle count threshold of 256. The correct value should be 0x4 or a
>> minimum cycle count threshold of 4.
>>
>> This work arounds the problem via storing 4 in drvdata->ccitmin on affected
>> systems where the TRCIDR3.CCITMIN has been 256, thus preserving cycle count
>> threshold granularity.
>>
>> These errata information has been updated in arch/arm64/silicon-errata.rst,
>> but without their corresponding configs because these have been implemented
>> directly in the driver.
>>
>> Cc: Catalin Marinas <catalin.marinas@arm.com>
>> Cc: Will Deacon <will@kernel.org>
>> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
>> Cc: Mike Leach <mike.leach@linaro.org>
>> Cc: James Clark <james.clark@arm.com>
>> Cc: Jonathan Corbet <corbet@lwn.net>
>> Cc: linux-doc@vger.kernel.org
>> Cc: coresight@lists.linaro.org
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-kernel@vger.kernel.org
>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>> ---
>>  Documentation/arch/arm64/silicon-errata.rst   | 10 ++++++
>>  .../coresight/coresight-etm4x-core.c          | 36 +++++++++++++++++++
>>  2 files changed, 46 insertions(+)
>>
> 
>> diff --git a/drivers/hwtracing/coresight/coresight-etm4x-core.c b/drivers/hwtracing/coresight/coresight-etm4x-core.c
>> index 7e307022303a..591fab73ee79 100644
>> --- a/drivers/hwtracing/coresight/coresight-etm4x-core.c
>> +++ b/drivers/hwtracing/coresight/coresight-etm4x-core.c
>> @@ -1131,6 +1131,39 @@ static void cpu_detect_trace_filtering(struct etmv4_drvdata *drvdata)
>>  	drvdata->trfcr = trfcr;
>>  }
>>  
>> +/*
>> + * The following errata on applicable cpu ranges, affect the CCITMIN filed
>> + * in TCRIDR3 register. Software read for the field returns 0x100 limiting
>> + * the cycle threshold granularity, where as the right value should have
> 
>                                        whereas
> 
>> + * been 0x4, which is well supported in the hardware.
>> + */
>> +static struct midr_range etm_wrong_ccitmin_cpus[] = {
>> +	/* Erratum #1490853 - Cortex-A76 */
>> +	MIDR_RANGE(MIDR_CORTEX_A76, 0, 0, 4, 0),
>> +	/* Erratum #1490853 - Neoverse-N1 */
>> +	MIDR_RANGE(MIDR_NEOVERSE_N1, 0, 0, 4, 0),
>> +	/* Erratum #1491015 - Cortex-A77 */
>> +	MIDR_RANGE(MIDR_CORTEX_A77, 0, 0, 1, 0),
>> +	/* Erratum #1502854 - Cortex-X1 */
>> +	MIDR_REV(MIDR_CORTEX_X1, 0, 0),
>> +	/* Erratum #1619801 - Neoverse-V1 */
>> +	MIDR_REV(MIDR_NEOVERSE_V1, 0, 0),
>> +	{},
>> +};
>> +
>> +static bool etm4_core_reads_wrong_ccitmin(struct etmv4_drvdata *drvdata)
>> +{
>> +	/*
>> +	 * Erratum affected cpus will read 256 as the minimum
>> +	 * instruction trace cycle counting threshold where as
> 
> 	                                              whereas

Right, 'whereas' is a single word indeed. I will change these as required.

  reply	other threads:[~2023-08-21  2:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18 11:20 [PATCH V4 0/3] coresight: etm: Make cycle count threshold user configurable Anshuman Khandual
2023-08-18 11:20 ` [PATCH V4 1/3] coresight: etm: Override TRCIDR3.CCITMIN on errata affected cpus Anshuman Khandual
2023-08-18 21:11   ` Randy Dunlap
2023-08-21  2:34     ` Anshuman Khandual [this message]
2023-08-18 11:20 ` [PATCH V4 2/3] coresight: etm: Make cycle count threshold user configurable Anshuman Khandual
2023-08-18 11:25   ` Suzuki K Poulose
2023-08-18 13:01     ` Mike Leach
2023-08-18 13:04       ` Suzuki K Poulose
2023-08-21  2:29         ` Anshuman Khandual
2023-08-18 11:20 ` [PATCH V4 3/3] Documentation: coresight: Add cc_threshold tunable Anshuman Khandual

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b6b76d8e-cce5-5d79-9488-645a5420558d@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=coresight@lists.linaro.org \
    --cc=james.clark@arm.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@linaro.org \
    --cc=rdunlap@infradead.org \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox