Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1237869pxf; Fri, 9 Apr 2021 03:38:55 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwjOWZvQ1d0h7V+NspQUw7S5VLBi0dQvPFWe472u6ggnDUjhWZfTcHk5eT+T5sjEeuaRdMf X-Received: by 2002:a17:907:700d:: with SMTP id wr13mr15807585ejb.310.1617964734784; Fri, 09 Apr 2021 03:38:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617964734; cv=none; d=google.com; s=arc-20160816; b=pDKnOE3EtYUjl5et/WEbAdiVOV6Ri3sSZqb7Xbk9DhKk3NW53Xz4VZClxrYGoroX5D 8ssPEoOUiszCCG/PyiCDz0wMWtrGZOoQICA8Gsx8roHPLUJcTvr6lYE1To6lH5t43Fz0 IhSk1O4tFKpYaM93Gb/+RYlhHKROQ4jT0P0xvBmAOn/Yji8NjEDNLMozmGRfXqvcONeu oORpqssNxRHuNfQnF2Rt4bzErJAKtnrSNiAkYcW1PV0uyY2PJcLsV8S+PVUCPzSNhots PnJzWyLxJjcrYQr3T5Fpa1bB07QhwlrLigv6Nswn04yIcwLHuiztRs4MUbd6XTlnhd8/ fq/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:subject:cc:to:from :dkim-signature; bh=HlnjO6SXiZ+lldSt8OyvhIex73WlhZohzXmWoXnSTsA=; b=UOAh6Dggx8dJaiU0IXurb7EYxWqNnDRy3JJ9NSzdQHoaQewVK2K1shtVrGD6dHVkFS Gi261ZAA/1HQ7esPPlHOa99glneWYpEPxFzYb0+yUDfWJQXad3mgdYUo+45dQj/YbHxK XCKE+FOujsmUZLSSIH4+FXejz7e24R4feRCwo+IYPgh4AimepGgUT4W+Z0vqEpF8eIxh V+w+J3hfGgyND9S/IKPmVRWlnWX7X31o39U/d9qct4p7MxXIDu3xlIpCz2i6JANi+hZw u3SpKFI9xbWpROa4Y3JbdVZjyEj0E+vkUArN3nkAw1HxRBG/btQj25qMFulw/rdirt7j /EHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=astWVqOH; 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 a20si1723503ejf.345.2021.04.09.03.38.31; Fri, 09 Apr 2021 03:38:54 -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; dkim=pass header.i=@linaro.org header.s=google header.b=astWVqOH; 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 S232690AbhDIKht (ORCPT + 99 others); Fri, 9 Apr 2021 06:37:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33888 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232286AbhDIKhp (ORCPT ); Fri, 9 Apr 2021 06:37:45 -0400 Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2CDDBC061760 for ; Fri, 9 Apr 2021 03:37:32 -0700 (PDT) Received: by mail-wm1-x32c.google.com with SMTP id z24-20020a1cf4180000b029012463a9027fso2709195wma.5 for ; Fri, 09 Apr 2021 03:37:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=HlnjO6SXiZ+lldSt8OyvhIex73WlhZohzXmWoXnSTsA=; b=astWVqOH/5XQCD3fTeONLzJo8WLBVrf1VfRjIZez1MElxzQdgmD0VpKyAEzE6rVrDM SBPmxrC0r9RIuEvEoOAmaOL87gxv/JwZ6G81WyKSm1BwER0c+qjQwExC+7BnYAi6oDqR y5AHIRj63rzIwaGtZa86hpR//OfLyQYZNYdlpeSR5EFvarclVlLeJzJpVbeX1F7958GG c1I5WxhGfxsvZikgpXDtPnaASDm9Ljd+sLb6DY4KDWC2WQU+p6ySu6tn2eO9Uwg2SrRc zkG//N8uLch2guZsBQDWz7xOEhe9IdE9Ml2FyrqB/jE+1RKSyJ/rvdOH20Nd3H+yxnwW 88NA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=HlnjO6SXiZ+lldSt8OyvhIex73WlhZohzXmWoXnSTsA=; b=qt3FVt0Y6yjh1IDodugv0I0zHKhSr5x2ELkuKnfg4FACYvuZYIglj1YMgodPbhDVhm HljzzNsdGBDaBiGkno3+35CZED3RepsO/eGvhi8hAyMFvSAKK5VGrozdsMtMMFFz46nY /GU45muoHiFWM+09y+SLFvcHZ0oKs9YblC9wWI6gxl1MDtlaeqSdZSiEtKE6foTzHGC1 4feUVQLP+H876gCMVm+T6wQQKI7cJ4mwxbZhiEGpO44gDoAFypM9HKehzxTd1CXpYRqG y+SbDuFN3/hGG4jek/mID7ahJyD2jgfYXi4Vmd/uO6ku/GMjhEf87h+ZSwHA3Sjyvggp hGDQ== X-Gm-Message-State: AOAM530iFfWV+Le+1uB/2mX6pOgBBzn57K6CFshFd5+yBmC86iB630Se JM20ER81TYTE7K0OlMUnIges6Q== X-Received: by 2002:a7b:c399:: with SMTP id s25mr262754wmj.97.1617964650883; Fri, 09 Apr 2021 03:37:30 -0700 (PDT) Received: from linaro.org ([2a00:23c5:6809:2201:20a6:106c:24d6:628]) by smtp.gmail.com with ESMTPSA id w7sm4087650wro.43.2021.04.09.03.37.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Apr 2021 03:37:30 -0700 (PDT) From: Mike Leach To: linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org, mathieu.poirier@linaro.org, linux-doc@vger.kernel.org, suzuki.poulose@arm.com Cc: yabinc@google.com, leo.yan@linaro.org, alexander.shishkin@linux.intel.com, tingwei@codeaurora.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, Mike Leach Subject: [PATCH v6 00/10] CoreSight configuration management; ETM strobing Date: Fri, 9 Apr 2021 11:37:12 +0100 Message-Id: <20210409103722.26290-1-mike.leach@linaro.org> X-Mailer: git-send-email 2.17.1 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patchset introduces initial concepts in CoreSight system configuration management support. to allow more detailed and complex programming to be applied to CoreSight systems during trace capture. Configurations consist of 2 elements:- 1) Features - programming combinations for devices, applied to a class of device on the system (all ETMv4), or individual devices. 2) Configurations - a set of programmed features used when the named configuration is selected. Features and configurations are declared as a data table, a set of register, resource and parameter requirements. Features and configurations are loaded into the system by the virtual cs_syscfg device. This then matches features to any registered devices and loads the feature into them. Individual device classes that support feature and configuration register with cs_syscfg. Once loaded a configuration can be enabled for a specific trace run. Configurations are registered with the perf cs_etm event as entries in cs_etm/events. These can be selected on the perf command line as follows:- perf record -e cs_etm// ... This patch set has one pre-loaded configuration and feature. A named "strobing" feature is provided for ETMv4. A named "autofdo" configuration is provided. This configuration enables strobing on any ETM in used. Thus the command: perf record -e cs_etm/autofdo/ ... will trace the supplied application while enabling the "autofdo" configuation on each ETM as it is enabled by perf. This in turn will enable strobing for the ETM - with default parameters. Parameters can be adjusted using configfs. The sink used in the trace run will be automatically selected. A configuration can supply up to 15 of preset parameter values, which will subsitute in parameter values for any feature used in the configuration. Selection of preset values as follows perf record -e cs_etm/autofdo,preset=1/ ... (valid presets 1-N, where N is the number supplied in the configuration, not exceeding 15. preset=0 is the same as not selecting a preset.) Applies to & tested against coresight/next-ETE-TRBE (5.12-rc3 base) Changes since v5: 1) Fix code style issues from auto-build reports, as Reported-by: kernel test robot 2) Update comments to get consistent docs for API functions. 3) remove unused #define from autofdo example. 4) fix perf code style issues from patch 4 (Mathieu) 5) fix configfs code style issues from patch 9. (Mathieu) Changes since v4: (based on comments from Matthieu and Suzuki). No large functional changes - primarily code improvements and naming schema. 1) Updated entire set to ensure a consistent naming scheme was used for variables and struct members that refer to the key objects in the system. Suffixes _desc used for all references to feature and configuraion descriptors, suffix _csdev used for all references to load feature and configs in the csdev instances. (Mathieu & Suzuki). 2) Dropped the 'configurations' sub dir in cs_etm perf directories as superfluous with the configfs containing the same information. (Mathieu). 3) Simplified perf handling code (suzuki) 4) Multiple simplifications and improvements for code readability (Matthieu and Suzuki) Changes since v3: (Primarily based on comments from Matthieu) 1) Locking mechanisms simplified. 2) Removed the possibility to enable features independently from configurations.Only configurations can be enabled now. Simplifies programming logic. 3) Configuration now uses an activate->enable mechanism. This means that perf will activate a selected configuration at the start of a session (during setup_aux), and disable at the end of a session (around free_aux) The active configuration and associated features will be programmed into the CoreSight device instances when they are enabled. This locks the configuration into the system while in use. Parameters cannot be altered while this is in place. This mechanism will be extended in future for dynamic load / unload of configurations to prevent removal while in use. 4) Removed the custom bus / driver as un-necessary. A single device is registered to own perf fs elements and configfs. 5) Various other minor issues addressed. Changes since v2: 1) Added documentation file. 2) Altered cs_syscfg driver to no longer be coresight_device based, and moved to its own custom bus to remove it from the main coresight bus. (Mathieu) 3) Added configfs support to inspect and control loaded configurations and features. Allows listing of preset values (Yabin Cui) 4) Dropped sysfs support for adjusting feature parameters on the per device basis, in favour of a single point adjustment in configfs that is pushed to all device instances. 5) Altered how the config and preset command line options are handled in perf and the drivers. (Mathieu and Suzuki). 6) Fixes for various issues and technical points (Mathieu, Yabin) Changes since v1: 1) Moved preloaded configurations and features out of individual drivers. 2) Added cs_syscfg driver to manage configurations and features. Individual drivers register with cs_syscfg indicating support for config, and provide matching information that the system uses to load features into the drivers. This allows individual drivers to be updated on an as needed basis - and removes the need to consider devices that cannot benefit from configuration - static replicators, funnels, tpiu. 3) Added perf selection of configuarations. 4) Rebased onto the coresight module loading set. To follow in future revisions / sets:- a) load of additional config and features by loadable module. b) load of additional config and features by configfs c) enhanced resource management for ETMv4 and checking features have sufficient resources to be enabled. d) ECT and CTI support for configuration and features. Mike Leach (10): coresight: syscfg: Initial coresight system configuration coresight: syscfg: Add registration and feature loading for cs devices coresight: config: Add configuration and feature generic functions coresight: etm-perf: update to handle configuration selection coresight: syscfg: Add API to activate and enable configurations coresight: etm-perf: Update to activate selected configuration coresight: etm4x: Add complex configuration handlers to etmv4 coresight: config: Add preloaded configurations coresight: syscfg: Add initial configfs support Documentation: coresight: Add documentation for CoreSight config .../trace/coresight/coresight-config.rst | 244 ++++++ Documentation/trace/coresight/coresight.rst | 16 + drivers/hwtracing/coresight/Makefile | 7 +- .../hwtracing/coresight/coresight-cfg-afdo.c | 147 ++++ .../coresight/coresight-cfg-preload.c | 27 + .../coresight/coresight-cfg-preload.h | 11 + .../hwtracing/coresight/coresight-config.c | 275 ++++++ .../hwtracing/coresight/coresight-config.h | 253 ++++++ drivers/hwtracing/coresight/coresight-core.c | 12 +- .../hwtracing/coresight/coresight-etm-perf.c | 150 +++- .../hwtracing/coresight/coresight-etm-perf.h | 12 +- .../hwtracing/coresight/coresight-etm4x-cfg.c | 182 ++++ .../hwtracing/coresight/coresight-etm4x-cfg.h | 30 + .../coresight/coresight-etm4x-core.c | 38 +- .../coresight/coresight-etm4x-sysfs.c | 3 + .../coresight/coresight-syscfg-configfs.c | 396 +++++++++ .../coresight/coresight-syscfg-configfs.h | 45 + .../hwtracing/coresight/coresight-syscfg.c | 804 ++++++++++++++++++ .../hwtracing/coresight/coresight-syscfg.h | 81 ++ include/linux/coresight.h | 7 + 20 files changed, 2704 insertions(+), 36 deletions(-) create mode 100644 Documentation/trace/coresight/coresight-config.rst create mode 100644 drivers/hwtracing/coresight/coresight-cfg-afdo.c create mode 100644 drivers/hwtracing/coresight/coresight-cfg-preload.c create mode 100644 drivers/hwtracing/coresight/coresight-cfg-preload.h create mode 100644 drivers/hwtracing/coresight/coresight-config.c create mode 100644 drivers/hwtracing/coresight/coresight-config.h create mode 100644 drivers/hwtracing/coresight/coresight-etm4x-cfg.c create mode 100644 drivers/hwtracing/coresight/coresight-etm4x-cfg.h create mode 100644 drivers/hwtracing/coresight/coresight-syscfg-configfs.c create mode 100644 drivers/hwtracing/coresight/coresight-syscfg-configfs.h create mode 100644 drivers/hwtracing/coresight/coresight-syscfg.c create mode 100644 drivers/hwtracing/coresight/coresight-syscfg.h -- 2.17.1