Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp356923pxb; Wed, 14 Apr 2021 17:42:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyd6Lv1i3BRJtnQcA499LChJtDF/G4EgJDugNUbcrawpQS7dqXj2jN3GHOswYBgIDqKZII7 X-Received: by 2002:a17:90a:94c4:: with SMTP id j4mr846956pjw.14.1618447360342; Wed, 14 Apr 2021 17:42:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618447360; cv=none; d=google.com; s=arc-20160816; b=O+qWIr18kmAsuJp/Clyg6Cfvapv35rXFwQ2vgsPKIFDtz2dfNZaSMlm1Ey1j3JYlCV sGAwq3ATPWUqs6+H1P1L6wwYL9oN3X22e2ZROZrgMIr03ShyeXtg0+dReZVIsuavEJuK o0FqHx4fyBUTpyeHU02xmy42lw49vIY9dZN5ygg0N+zIibrZ3BPlbVW6oaA5hnnYa7Ql p1lWyn3TrFxdYYzMg4eO7tlyEo9Ga+0XNN0Uw19Eh2OpyxobHiVXeB+btJ2zixmQaca5 0w6s+QWBR+o6/IANRUtOsX/jx3EMBHW7MlEFSS+35qCTSTzrJmgsM+opS8g4pkuhumkG Pa/w== 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=wzQ7aFO9CmJbwruZGwwKMP0v5PNaSPnUfL07kSjFRnI=; b=0u+8zd2p7jcseU3gGUo+X/zlDQQpfX2ahi150z88fwoQHDctgA/Nze1cyF2Qb4WZ3l 3kWIphcASm+BEYAuxv5atLpx2f7/8ncj9MtGIr3gNxE75cvwXf1Tjw0LdoEnUBNf9+Lx qZ65pITqmuL8s8EaFfgocaI6La+AfAy9th4UHTjZ7qn3K1+zBoy2rf9ZniNSP3mfC9Hq ktkJ4OxRLSeaN5zzAEzqzB/w1T54DF1caoi4dxu2J5jRP6F9gpLbGagqQR9I8M/7UGoY mH7lCAlxkemo+S/66kibmkNR6ASRz8DulL6v07E5u0XRZXSmhW8VoB1gbtO9IenMHeqA LvQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=Ty3NJe00; 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 n13si1111497pgq.426.2021.04.14.17.42.28; Wed, 14 Apr 2021 17:42:40 -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=Ty3NJe00; 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 S233324AbhDNTTb (ORCPT + 99 others); Wed, 14 Apr 2021 15:19:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41420 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230040AbhDNTT3 (ORCPT ); Wed, 14 Apr 2021 15:19:29 -0400 Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AF8A4C061574 for ; Wed, 14 Apr 2021 12:19:07 -0700 (PDT) Received: by mail-wr1-x435.google.com with SMTP id m9so8187917wrx.3 for ; Wed, 14 Apr 2021 12:19:07 -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=wzQ7aFO9CmJbwruZGwwKMP0v5PNaSPnUfL07kSjFRnI=; b=Ty3NJe00pdywQtlTyJEvOG+lpEoLTptNksf/9Onjjl7peYr3aJzhFiYS8zUD3fUrCy U3sRaKcREHls68bagHfwj+TfE9ymF2TJqcHoqKcTeTczPovw+rYQrh3QjfYxWaWHWDFt njsXmFvzVksLSoEKzMEdDvzls6TeZ4KtFkxkGG15bBUWl0qQYU7pyZ29n2fSsoPJmqrX z28npFvNtYugDmNiSlNy06Y6dZHlhetN1+5eLhErFoHqUlHsb5Dv+mJMj0fpUE+U6U6D 1fs54yEAgP6G00+v2hHs3YyploPv1d2sg5xiu0YYk9iQV3GC4pkvBtxWCAvxSA7axZUc oTQw== 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=wzQ7aFO9CmJbwruZGwwKMP0v5PNaSPnUfL07kSjFRnI=; b=UhvZASlYZGkAV4P0VSckIvGPXYoGz2yzRDoR5A8Cg9CtYGSvYElW4X7sj3lgALSKrg 8T0z5Vnb+kWzjozthoY6cQ1USaoFCyqLrNrPMSgXmusetzJtiWZrYympRYEv2AiMVtyb ZegfJ9CqZ2eVHBeQPsa/37V4Zbz6CZpFPB6+On8PM7xxodmkVNybFLGEEBcCeqbJLbV5 LFM3ySbEc3cqqT20nW+NCpZxNjj8HQ6SGKzI/2BPEIzqWDYBaD+SCsGmCFuncaWPMO8U clav7/JfKcU2dgVwLqXxaHz9HcjGVaUV6WLXpKhynmmLITJTrmQn7Y0XBBXKgYvW8ERd jKwg== X-Gm-Message-State: AOAM532hMEaD6BDtsnRWoorGxlKbIVHqq9E4HaviW4eZ0SKdi7fcofZL rY3Fg+JnnyotnkPZM0VmIcGUmA== X-Received: by 2002:adf:f04d:: with SMTP id t13mr19455695wro.52.1618427946396; Wed, 14 Apr 2021 12:19:06 -0700 (PDT) Received: from linaro.org ([2a00:23c5:6809:2201:546d:7d59:1703:bf96]) by smtp.gmail.com with ESMTPSA id a3sm327073wru.40.2021.04.14.12.19.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 14 Apr 2021 12:19:05 -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, corbet@lwn.net, leo.yan@linaro.org, alexander.shishkin@linux.intel.com, tingwei@codeaurora.org, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, Mike Leach Subject: [PATCH v7 00/10] CoreSight configuration management; ETM strobing Date: Wed, 14 Apr 2021 20:18:53 +0100 Message-Id: <20210414191903.18349-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 v6: Fixed kernel test robot issues- Reported-by: kernel test robot 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 | 153 ++++ .../coresight/coresight-cfg-preload.c | 31 + .../coresight/coresight-cfg-preload.h | 13 + .../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, 2716 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