Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp6215291pxv; Thu, 29 Jul 2021 09:03:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyoU49zPjru5aLWbg/i3GD/Ou8TeaZ7c74LGw4CXZk6VuxqWCZffOoeiy5idWjawzBXAm9t X-Received: by 2002:a17:906:abcb:: with SMTP id kq11mr5368860ejb.214.1627574610427; Thu, 29 Jul 2021 09:03:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627574610; cv=none; d=google.com; s=arc-20160816; b=qMSjly/g1uI9hdjuSeyTPwWNm3sCUgG9i6j18fzROkh9ERsAFyTCCvadiZ+HvnyX9o Zkosj+HalPE/8r/iEZk/vNqmHIYCEIqJj7Jx1oZY3Oh2DfHs2tMni1hIisKfbHVolgwq 1qDbR6QmoN8dv3vefiA9Eu3BlQparaCwauf8xB1Sh8h/pntp4FN6bwWT9LTBXlGO2Ek6 iNv2Wg/YK//lqEaKBWLF9zI52Ref7n4NYNA2Dl5S6iYb1fiSRxrT3cOLE300ORRGV0YW rUFl3kDYBFtkPSRwRz5FJMxsjmrEg9zoIxkRjuqX9PEj0LxI9bvOJDdgMXhS9ivfv07E 6DhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=Oa7JP3S86MPsutF9MMYXlYxMOC5aEK+E4VbS1ljqCYQ=; b=y6UPacfD4iGnHQFe1JJm5Y/CoQf11nNW/cqnTflBnQMsqpyMSKAhfDea4Er6kTf3DP K0kfgkTFZwe9S1d8urlYrwEQjxZ+rycxqTKsJ1Z/cSLKOPa6UgHlVI6GTh8+FB2yIPsL Z/W3sizmGelWZHxMS3D+Jc9IhJFgjTTXqm+TFCyyRjBJhz4Apty1IIm5kcren4fCcReC S+jksD/yQn9f0PcmMfZzJYH2473k5CbHf28CaNz1XiEB51ROVujvqVsjK3rPZrdb1SMo Na+Ocf746+vVXlm3pjn5fROKyyKAwbb8HtOj4YM7grNw9VCHRA752AnY1hR5ndfEHu68 JRqw== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f17si3337251ejz.260.2021.07.29.09.03.05; Thu, 29 Jul 2021 09:03:30 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231193AbhG2QA7 (ORCPT + 99 others); Thu, 29 Jul 2021 12:00:59 -0400 Received: from foss.arm.com ([217.140.110.172]:51310 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238333AbhG2P6r (ORCPT ); Thu, 29 Jul 2021 11:58:47 -0400 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 16F0C1FB; Thu, 29 Jul 2021 08:58:44 -0700 (PDT) Received: from e121896.arm.com (unknown [10.57.40.10]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 6BDFB3F73D; Thu, 29 Jul 2021 08:58:41 -0700 (PDT) From: James Clark To: acme@kernel.org, mathieu.poirier@linaro.org, coresight@lists.linaro.org, linux-perf-users@vger.kernel.org Cc: leo.yan@linaro.org, suzuki.poulose@arm.com, mike.leach@linaro.org, James Clark , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , John Garry , Will Deacon , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [RFC PATCH 0/6] perf tools: Warning fixes Date: Thu, 29 Jul 2021 16:57:59 +0100 Message-Id: <20210729155805.2830-1-james.clark@arm.com> X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I'm submitting this as an RFC because there are a few changes I'd like to get feedback on. The two changes I wanted to make were the last two for Coresight warnings, but I ended up making some perf-wide changes along the way. For #1 (perf tools: Add WARN_ONCE equivalent for UI warnings) * Does it make sense to add warn once equivalents at all, or should the once be re-done for each usage? * Or should there be some kind of generic 'once' wrapper? For #3 (perf tools: Add disassembly warnings for annotate --stdio) * If the output is interpreted by any other tools, then adding these warnings could be an issue, so maybe this change could be dropped, but no error output at all isn't ideal. For #4 (perf tools: Add flag for tracking warnings of missing DSOs) * In theory I could re-use 'annotate_warned', but it might make sense to rename it in that case, or just leave the new auxtrace_warned and remove any confusion. This set applies to perf/core e73f0f0ee7541 Thanks James James Clark (6): perf tools: Add WARN_ONCE equivalent for UI warnings perf tools: Re-add annotate_warned functionality perf tools: Add disassembly warnings for annotate --stdio perf tools: Add flag for tracking warnings of missing DSOs perf cs-etm: Improve Coresight zero timestamp warning perf cs-etm: Add warnings for missing DSOs tools/perf/ui/browsers/annotate.c | 1 + tools/perf/ui/gtk/annotate.c | 1 + tools/perf/util/annotate.c | 20 +++++++++++++++++-- .../perf/util/cs-etm-decoder/cs-etm-decoder.c | 7 +++++-- tools/perf/util/cs-etm.c | 10 +++++++++- tools/perf/util/debug.h | 14 +++++++++++++ tools/perf/util/dso.h | 1 + 7 files changed, 49 insertions(+), 5 deletions(-) -- 2.28.0