Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp726485pxu; Thu, 7 Jan 2021 17:11:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJyQfgvpHnyBaJvRz7MbBki2m86LoBjpZWJyjPns9HYks5FB9WhPQD9nZfIb06geeaLFNGdG X-Received: by 2002:a05:6402:22b4:: with SMTP id cx20mr3580920edb.262.1610068297878; Thu, 07 Jan 2021 17:11:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610068297; cv=none; d=google.com; s=arc-20160816; b=nRLoR8s+xxlYirrKkbG+ce9wZoqXV8ZKydQYkZHlZyF+BGLDyDFFWoAFXpPgj6b6n5 wYdEVwjFPw5HuNkm29/CDQVDMROQqF9F+nSk+b2Uq/FvLIjXYIBH2GfHUcbHL8O2sgl5 8sg2hyPYstB/t+Rl759/rBJD3nxnZDBHY4ZAM0oKGIbGBx8y2oZ10CN7Q59saydrRcqT IRWoN9UgupFl5Ew0hPbm95SkCi2Av8dhIIx2ibIhPieM/PnHaTn1JOzvmyxveP4/wwoB jlYUbBHMtfFBHfXoH9RVc6F50V/x7sX4U1WUdqrTa68DJqEdtmyuTf49GINi46vDpQJP 9Jcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=3s0tWg/+h/coov5XuJdVQbTVm+GIFoyKRvTW1DF+MZw=; b=Y2oJJbIS5L2Fs16zvpvgJ7KGGN/NxkuqluQikKfgpa1o0fM/sS8QKGep/IVjNlrxN4 vUkNhbuCEI+DNXXgaWku+rXZyaDRi45SuV0yVPNxdnu8oqCjai3YBvuG7qAwmvHEmXz1 TlaNNY6NEN1AC5xPOx+9Mz2Bs02MEF1kq1PGIx++FRDpRXWYH37ZvRZ0FuPWtkDjNfHg wweIBpIexmCazuhlMKuMZydrswXm2bib5YjVfCUcR5ZJAQmZkK56we+29utrmXS/V4Kk FE6lb/ZtgH8U2Cs/RKi0mlShQl7kf1m5DLLYgFHPK3V6bTr6UI/YZHCNHF3CU/BIKdEe N93A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=x5BSjhOE; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t12si572499eju.194.2021.01.07.17.11.14; Thu, 07 Jan 2021 17:11:37 -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; dkim=pass header.i=@linaro.org header.s=google header.b=x5BSjhOE; 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=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729757AbhAHBJv (ORCPT + 99 others); Thu, 7 Jan 2021 20:09:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43928 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729564AbhAHBJu (ORCPT ); Thu, 7 Jan 2021 20:09:50 -0500 Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 69A83C0612F4 for ; Thu, 7 Jan 2021 17:09:10 -0800 (PST) Received: by mail-pg1-x52c.google.com with SMTP id z21so6560326pgj.4 for ; Thu, 07 Jan 2021 17:09:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=3s0tWg/+h/coov5XuJdVQbTVm+GIFoyKRvTW1DF+MZw=; b=x5BSjhOE9fipibgX/YJ/Ako8BNNnt4Tgp5PggyjdqA+/nxteXeQgVfcJljZxB13OxS MLV1+Xar8eATjoIZrDi7pQWBpxszUIfBjTBnHjXMo7RJM4kNhnTxx2PbPx4SH2Ifpdgh fgB9VjisfP7jN9v9CxUFHRC3cZQwMPR0p771qXpW/8ULwiAujzXN1o/B0aGGcz//ZOLQ PQNsiNotKzb6zFpHxFzGs3Dls9KiS3JCrhnOaIrU8GyRet1sQBfKEMvYYR1JV2GSs6aC ydRADMev57SRAT72L7R2ZiAx28KOiOomqSwlgC6viGltWudkI8cyF/hKbuFm2hMEsUqU vUPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=3s0tWg/+h/coov5XuJdVQbTVm+GIFoyKRvTW1DF+MZw=; b=TMLwsU0F7O2gDrkdF6qYq6BJlirk8I6QIh2NudgEwZnYanVVThfX4pRYdbGB3Bz38T 5nZJ5NfC2p7KCbMjuSJ7aWueqWCZcg1sPPz8eTrmOKRtfGqkSTa5xCu+gfY6zZl+obKl oyRzBeOkGW2QSXzPQJxvlcPsPVpZncEu0jmyMHVtrRY4ePUy0lG390zfafI2stcU/K0o NCL9JTK95fGs+JOWWNW+uRtNgqXbO80TURrWZp+tIyM2y9eynmW8ov5YTDD55dAl3IUa 34pPMRYaQLIh64PNpTVKGE7b8jYAtC41h6LoVBIegbXLLolf1dwriVDdTcBKS2jSgT09 DDaA== X-Gm-Message-State: AOAM530YPW4N5/VsUD08NjxWWdix3f/bo948jBnYOFGrFq67y4VaIquK JxnASSstHP8XCvpPbX1mOoXKlg== X-Received: by 2002:aa7:82cc:0:b029:19e:1328:d039 with SMTP id f12-20020aa782cc0000b029019e1328d039mr4618622pfn.70.1610068149882; Thu, 07 Jan 2021 17:09:09 -0800 (PST) Received: from xps15 (S0106889e681aac74.cg.shawcable.net. [68.147.0.187]) by smtp.gmail.com with ESMTPSA id x127sm6467502pfb.74.2021.01.07.17.09.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 07 Jan 2021 17:09:08 -0800 (PST) Date: Thu, 7 Jan 2021 18:09:07 -0700 From: Mathieu Poirier To: Suzuki K Poulose Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, coresight@lists.linaro.org, leo.yan@linaro.org, mike.leach@linaro.org, anshuman.khandual@arm.com Subject: Re: [PATCH v6 00/26] coresight: etm4x: Support for system instructions Message-ID: <20210108010907.GJ43045@xps15> References: <20210107123859.674252-1-suzuki.poulose@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210107123859.674252-1-suzuki.poulose@arm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Suzuki, On Thu, Jan 07, 2021 at 12:38:33PM +0000, Suzuki K Poulose wrote: > CoreSight ETMv4.4 obsoletes memory mapped access to ETM and > mandates the system instructions for registers. > This also implies that they may not be on the amba bus. > Right now all the CoreSight components are accessed via memory > map. Also, we have some common routines in coresight generic > code driver (e.g, CS_LOCK, claim/disclaim), which assume the > mmio. In order to preserve the generic algorithms at a single > place and to allow dynamic switch for ETMs, this series introduces > an abstraction layer for accessing a coresight device. It is > designed such that the mmio access are fast tracked (i.e, without > an indirect function call). > > This will also help us to get rid of the driver+attribute specific > sysfs show/store routines and replace them with a single routine > to access a given register offset (which can be embedded in the > dev_ext_attribute). This is not currently implemented in the series, > but can be achieved. > > Further we switch the generic routines to work with the abstraction. > With this in place, we refactor the etm4x code a bit to allow for > supporting the system instructions with very little new code. > > We use TRCDEVARCH for the detection of the ETM component, which > is a standard register as per CoreSight architecture, rather than > the etm specific id register TRCIDR1. This is for making sure > that we are able to detect the ETM via system instructions accurately, > when the the trace unit could be anything (etm or a custom trace unit). > To keep the backward compatibility for any existing broken > impelementation which may not implement TRCDEVARCH, we fall back to TRCIDR1. > Also this covers us for the changes in the future architecture [0]. > > Also, v8.4 self-hosted tracing extensions (coupled with ETMv4.4) adds > new filtering registers for trace by exception level. So on a v8.4 > system, with Trace Filtering support, without the appropriate > programming of the Trace filter registers (TRFCR_ELx), tracing > will not be enabled. This series also includes the TraceFiltering > support to cover the ETM-v4.4 support. > > The series has been mildly tested on a model for system instructions. > I would really appreciate any testing on real hardware. I have queued your work in my local tree. I will have a final pass before pushing to coresight-next tomorrow or on Monday. Thanks, Mathieu > > Applies on coresight/next. A tree is available here [1]. > > [0] https://developer.arm.com/docs/ddi0601/g/aarch64-system-registers/trcidr1 > [1] https://gitlab.arm.com/linux-arm/linux-skp coresight/etm/sysreg-v6 > > Changes since v5: > - Rebased on to coresight/next. > - Moved trcdevarch to mgmt/ in sysfs and updated the sysfs ABI > document (Mike Leach) > - New patch : Moved the etm4_check_arch_features to run on the CPU, since > the PID of the ETM has to be read on the CPU and is unavailable > otherwise. > > Changes since v4: > - Fix typo in commit description for the patches 02 & 15 > - Refactor the AMBA device "remove" call back for use with > paltform_driver. (patch 21). Thus remove Review tag by Mathieu, > even though the changes are minimal. > - Added "remove" callback for platform_driver in patch 22, removed > Review tag by Mathieu > - Add 'U' suffix for constants in Patch 24 (Catalin) > - Fixed field extraction in Patch 25 > > Changes since v3: > - Device tree compatible changed to etm4x > - Use etm4x_** instead of generalizing etm_ in etm4x driver. > - Added v8.4 self hosted trace support patches, reworked > from Jonathan's series. > - Dropped queued patches. > - Expose TRCDEVARCH via trcidr, as this will be needed for > the userspace tools to determine the trace major/minor > arch versions. > - Remove csa argument to read()/write() (Mathieu) > - Fix secure exception mask calculation (Mathieu) > - Fix various coding style comments (Mathieu) > (See individual patches for change log) > > Changes since V2: > - Several fixes to the ETM register accesses. Access a register > when it is present. > - Add support for TRCIDR3.NUMPROCS for v4.2+ > - Drop OS lock detection. Use software lock only in case of mmio. > - Fix issues with the Exception level masks (Mike Leach) > - Fall back to using TRCIDR1 when TRCDEVARCH is not "present" > - Use a generic notion of ETM architecture (rather than using > the encoding as in registers) > - Fixed some checkpatch issues. > - Changed the dts compatible string to "arm,coresight-etm-sysreg" > (Mike Leach) > > Changes since V1: > - Flip the switch for iomem from no_iomem to io_mem in csdev_access. > - Split patches for claim/disclaim and CS_LOCK/UNLOCK conversions. > - Move device access initialisation for etm4x to the target CPU > - Cleanup secure exception level mask handling. > - Switch to use TRCDEVARCH for ETM component discovery. This > is for making > - Check the availability of OS/Software Locks before using them. > > Known issues: > Checkpatch failure for "coresight: etm4x: Add sysreg access helpers" : > > ERROR: Macros with complex values should be enclosed in parentheses > #121: FILE: drivers/hwtracing/coresight/coresight-etm4x.h:153: > +#define CASE_READ(res, x) \ > + case (x): { (res) = read_etm4x_sysreg_const_offset((x)); break; } > > I don't know a way to fix the warning without loosing the code > readability, which I believe is crucial for such a construct. > > > > Jonathan Zhou (2): > arm64: Add TRFCR_ELx definitions > coresight: Add support for v8.4 SelfHosted tracing > > Suzuki K Poulose (24): > coresight: etm4x: Handle access to TRCSSPCICRn > coresight: etm4x: Skip accessing TRCPDCR in save/restore > coresight: Introduce device access abstraction > coresight: tpiu: Prepare for using coresight device access abstraction > coresight: Convert coresight_timeout to use access abstraction > coresight: Convert claim/disclaim operations to use access wrappers > coresight: etm4x: Always read the registers on the host CPU > coresight: etm4x: Convert all register accesses > coresight: etm4x: Add commentary on the registers > coresight: etm4x: Add sysreg access helpers > coresight: etm4x: Define DEVARCH register fields > coresight: etm4x: Check for Software Lock > coresight: etm4x: Cleanup secure exception level masks > coresight: etm4x: Clean up exception level masks > coresight: etm4x: Handle ETM architecture version > coresight: etm4x: Detect access early on the target CPU > coresight: etm4x: Use TRCDEVARCH for component discovery > coresight: etm4x: Expose trcdevarch via sysfs > coresight: etm4x: Add necessary synchronization for sysreg access > coresight: etm4x: Detect system instructions support > coresight: etm4x: Refactor probing routine > coresight: etm4x: Run arch feature detection on the CPU > coresight: etm4x: Add support for sysreg only devices > dts: bindings: coresight: ETM system register access only units > > .../testing/sysfs-bus-coresight-devices-etm4x | 8 + > .../devicetree/bindings/arm/coresight.txt | 5 +- > arch/arm64/include/asm/sysreg.h | 11 + > drivers/hwtracing/coresight/coresight-catu.c | 12 +- > drivers/hwtracing/coresight/coresight-core.c | 122 ++- > .../hwtracing/coresight/coresight-cti-core.c | 18 +- > drivers/hwtracing/coresight/coresight-etb10.c | 10 +- > .../coresight/coresight-etm3x-core.c | 9 +- > .../coresight/coresight-etm4x-core.c | 805 ++++++++++++------ > .../coresight/coresight-etm4x-sysfs.c | 46 +- > drivers/hwtracing/coresight/coresight-etm4x.h | 498 ++++++++++- > .../hwtracing/coresight/coresight-funnel.c | 7 +- > .../coresight/coresight-replicator.c | 13 +- > drivers/hwtracing/coresight/coresight-stm.c | 4 +- > .../hwtracing/coresight/coresight-tmc-core.c | 16 +- > .../hwtracing/coresight/coresight-tmc-etf.c | 10 +- > .../hwtracing/coresight/coresight-tmc-etr.c | 4 +- > drivers/hwtracing/coresight/coresight-tpiu.c | 31 +- > include/linux/coresight.h | 225 ++++- > 19 files changed, 1423 insertions(+), 431 deletions(-) > > -- > 2.24.1 >