Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp902227rwb; Thu, 19 Jan 2023 04:17:17 -0800 (PST) X-Google-Smtp-Source: AMrXdXsdAOrPoyAYraEwhFIfdktYtfY/LoWwJnrXxaqK1xaxBRnBPmQ9hchBAgVPUYLLohhee/EX X-Received: by 2002:a17:90b:394c:b0:226:e466:9e9b with SMTP id oe12-20020a17090b394c00b00226e4669e9bmr11369641pjb.4.1674130637007; Thu, 19 Jan 2023 04:17:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1674130636; cv=none; d=google.com; s=arc-20160816; b=DYgCAkJ4gkcjA32GraWPKRyNQ0lUVvt1vmtUP6Yk/xZ68dfyasM4GSC2O1wz4qJDD2 0BbgSj5wNl/poBCFr75AgiXF0K+6n/r4s75BpckskmnIM+aOyOGYB6Ptp2NuGUjc8j7c TPm0HYHhXN0zJMjzpeNK5AVKY5ic5b4okTmFGj5+ZPdgf+EeYGASNgwVrn4i9qvbyD4F eZJ7Yyl8ZwHShBeGMW88HZ0XYpIUNIdVANIiP90tw8rNQLNcuO2oq+k5ITbvxYIu6RQX Ikez073MRsa9ZD1gUX8GILDluAmJ2D7PhemiDyoATb2ZRlABsGzLYWIJV8ao2ZDcJWgU 5vnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:subject:user-agent:mime-version:date:message-id; bh=d09jb+91+V8cvBKNC4s4boDbcfPN86XTHPiZKkMZmAw=; b=rPCdlcbxeARicPDhMb+aWjocwn7Z2QfeNAnf5eWumcUKZ512N/fmcHvr5uTVKRzQRL Zs/G8Lu52IrCesonbL+I0b9k5Jj9ScBTn7nT9TwKH+o+gt2NywpzBIyt7+sp5OuKv4Az 07y+YSDk/A/ilSWBVwf1Rp/JIaoUG5xCt982OBMk2Fo2qyDznp+YwyfxNEV1Hu2v0Tzl ekJk20XISPU7zuoAyY4jVSLbHNvw1Ektbf67YSJJHsu+guk4+CJGmD8oMLg+DCa7BVFp 9XEs/DMW5C2w9RYR9vpBPiIHYDNSJ6ska5e2aknvTughNhFAzHEWqH2EdEzqoQj12bCp S8bA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p11-20020a654bcb000000b00478c967a865si39828970pgr.125.2023.01.19.04.17.11; Thu, 19 Jan 2023 04:17:16 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S229711AbjASMAV (ORCPT + 45 others); Thu, 19 Jan 2023 07:00:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35036 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230108AbjASMAN (ORCPT ); Thu, 19 Jan 2023 07:00:13 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id ED18E6F88E; Thu, 19 Jan 2023 04:00:04 -0800 (PST) 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 C9267176A; Thu, 19 Jan 2023 04:00:45 -0800 (PST) Received: from [10.57.75.229] (unknown [10.57.75.229]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9441D3F71A; Thu, 19 Jan 2023 04:00:02 -0800 (PST) Message-ID: <546f218f-3ac9-8fc2-c843-2f2f16882f31@arm.com> Date: Thu, 19 Jan 2023 12:00:00 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v7 00/15] coresight: Add new API to allocate trace source ID values To: Mike Leach , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo Cc: mathieu.poirier@linaro.org, peterz@infradead.org, mingo@redhat.com, linux-perf-users@vger.kernel.org, leo.yan@linaro.org, quic_jinlmao@quicinc.com References: <20230116124928.5440-1-mike.leach@linaro.org> From: Suzuki K Poulose In-Reply-To: <20230116124928.5440-1-mike.leach@linaro.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Arnaldo, On 16/01/2023 12:49, Mike Leach wrote: > The current method for allocating trace source ID values to sources is > to use a fixed algorithm for CPU based sources of (cpu_num * 2 + 0x10). > The STM is allocated ID 0x1. > > This fixed algorithm is used in both the CoreSight driver code, and by > perf when writing the trace metadata in the AUXTRACE_INFO record. > > The method needs replacing as currently:- > 1. It is inefficient in using available IDs. > 2. Does not scale to larger systems with many cores and the algorithm > has no limits so will generate invalid trace IDs for cpu number > 44. > > Additionally requirements to allocate additional system IDs on some > systems have been seen. > > This patch set introduces an API that allows the allocation of trace IDs > in a dynamic manner. > > Architecturally reserved IDs are never allocated, and the system is > limited to allocating only valid IDs. > > Each of the current trace sources ETM3.x, ETM4.x and STM is updated to use > the new API. > > For the ETMx.x devices IDs are allocated on certain events > a) When using sysfs, an ID will be allocated on hardware enable, or a read of > sysfs TRCTRACEID register and freed when the sysfs reset is written. > > b) When using perf, ID is allocated on during setup AUX event, and freed on > event free. IDs are communicated using the AUX_OUTPUT_HW_ID packet. > The ID allocator is notified when perf sessions start and stop > so CPU based IDs are kept constant throughout any perf session. > > > Note: This patchset breaks some backward compatibility for perf record and > perf report. > > The version of the AUXTRACE_INFO has been updated to reflect the fact that > the trace source IDs are generated differently. This will > mean older versions of perf report cannot decode the newer file. > > Appies to coresight/next > > Changes since v6: > 1) Export perf_report_aux_output_id() Acked by Peter, > 2) Update to ETMv3 docs requested by suzuki > 3) rebased and re-tested on coresight/next (6.2-rc2) > > Changes since v5: (requested by suzuki) > 1) Prefer odd ID values for system IDs to avoid overlap with legacy CPU IDs > 2) Some style changes > > Changes since v4: > 1) update to ensure that compiling after each individual patch added still > works - ie. git bisect not broken through the patchset.. > > 2) Revision to some of the now redundant code in cs-etm (James) > > 3) Comments and other minor fixes requested by Suzuki. > > Changes since v3: > 1) Fixed aarch32 build error in ETM3.x driver. > Reported-by: kernel test robot > > Changes since v2: > 1) Improved backward compatibility: (requested by James) > > Using the new version of perf on an old kernel will generate a usable file > legacy metadata values are set by the new perf and will be used if mew > ID packets are not present in the file. > > Using an older version of perf / simpleperf on an updated kernel may still > work. The trace ID allocator has been updated to use the legacy ID values > where possible, so generated file and used trace IDs will match up to the > point where the legacy algorithm is broken anyway. > > 2) Various changes to the ID allocator and ID packet format. > (suggested by Suzuki) > > 3) per CPU ID info in allocator now stored as atomic type to allow a passive read > without taking the allocator spinlock. perf flow now allocates and releases ID > values in setup_aux / free_event. Device enable and event enable use the passive > read to set the allocated values. This simplifies the locking mechanisms on the > perf run and fixes issues that arose with locking dependencies. > > Changes since v1: > (after feedback & discussion with Mathieu & Suzuki). > > 1) API has changed. The global trace ID map is managed internally, so it > is no longer passed in to the API functions. > > 2) perf record does not use sysfs to find the trace IDs. These are now > output as AUX_OUTPUT_HW_ID events. The drivers, perf record, and perf report > have been updated accordingly to generate and handle these events. > > Mike Leach (15): > coresight: trace-id: Add API to dynamically assign Trace ID values > coresight: Remove obsolete Trace ID unniqueness checks > coresight: perf: traceid: Add perf ID allocation and notifiers > coresight: stm: Update STM driver to use Trace ID API > coresight: etm4x: Update ETM4 driver to use Trace ID API > coresight: etm3x: Update ETM3 driver to use Trace ID API > coresight: etmX.X: stm: Remove trace_id() callback > coresight: trace id: Remove legacy get trace ID function. > perf: cs-etm: Move mapping of Trace ID and cpu into helper function > perf: cs-etm: Update record event to use new Trace ID protocol > kernel: events: Export perf_report_aux_output_id() > perf: cs-etm: Handle PERF_RECORD_AUX_OUTPUT_HW_ID packet > coresight: events: PERF_RECORD_AUX_OUTPUT_HW_ID used for Trace ID > coresight: trace-id: Add debug & test macros to Trace ID allocation > coresight: etm3x: docs: Alter sysfs documentation for trace id updates I have pushed the kernel patches on this series to coresight tree next[0]. I will be sending them out to Greg for v6.3. Please could you queue the perf tool changes in the series ? i.e., Patches 9,10 and 12. [0] https://git.kernel.org/pub/scm/linux/kernel/git/coresight/linux.git/log/?h=next Kind regards Suzuki