From: Stephane Eranian <eranian@google.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, kim.phillips@amd.com, acme@redhat.com,
jolsa@redhat.com, songliubraving@fb.com, mpe@ellerman.id.au,
maddy@linux.ibm.com
Subject: [PATCH v4 11/14] perf evsel: Make evsel__env always return a valid env
Date: Fri, 10 Dec 2021 13:02:26 -0800 [thread overview]
Message-ID: <20211210210229.2991238-12-eranian@google.com> (raw)
In-Reply-To: <20211210210229.2991238-1-eranian@google.com>
From: Kim Phillips <kim.phillips@amd.com>
It's possible to have an evsel and evsel->evlist populated without
an evsel->evlist->env, when, e.g., cmd_record is in its error path.
Future patches will add support for evsel__open_strerror to be able
to customize error messaging based on perf_env__{arch,cpuid}, so
let's have evsel__env return &perf_env instead of NULL in that case.
Signed-off-by: Kim Phillips <kim.phillips@amd.com>
---
tools/perf/util/evsel.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
index ac0127be0459..bb122979ef2c 100644
--- a/tools/perf/util/evsel.c
+++ b/tools/perf/util/evsel.c
@@ -2966,7 +2966,7 @@ int evsel__open_strerror(struct evsel *evsel, struct target *target,
struct perf_env *evsel__env(struct evsel *evsel)
{
- if (evsel && evsel->evlist)
+ if (evsel && evsel->evlist && evsel->evlist->env)
return evsel->evlist->env;
return &perf_env;
}
--
2.34.1.173.g76aa8bc2d0-goog
next prev parent reply other threads:[~2021-12-10 21:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 21:02 [PATCH v4 00/14] perf/x86/amd: Add AMD Fam19h Branch Sampling support Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 01/14] perf/core: add perf_clear_branch_entry_bitfields() helper Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 02/14] x86/cpufeatures: add AMD Fam19h Branch Sampling feature Stephane Eranian
2021-12-10 21:21 ` Borislav Petkov
2021-12-10 21:25 ` Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 03/14] perf/x86/amd: add AMD Fam19h Branch Sampling support Stephane Eranian
2021-12-29 9:54 ` Like Xu
2022-01-03 23:24 ` Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 04/14] perf/x86/amd: add branch-brs helper event for Fam19h BRS Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 05/14] perf/x86/amd: enable branch sampling priv level filtering Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 06/14] perf/x86/amd: add AMD branch sampling period adjustment Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 07/14] perf/x86/amd: make Zen3 branch sampling opt-in Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 08/14] ACPI: add perf low power callback Stephane Eranian
2021-12-13 5:56 ` kernel test robot
2021-12-13 22:40 ` kernel test robot
2021-12-23 13:11 ` Like Xu
2021-12-10 21:02 ` [PATCH v4 09/14] perf/x86/amd: add idle hooks for branch sampling Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 10/14] perf tools: add branch-brs as a new event Stephane Eranian
2021-12-10 21:02 ` Stephane Eranian [this message]
2021-12-10 21:02 ` [PATCH v4 12/14] perf tools: Improve IBS error handling Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 13/14] perf tools: Improve error handling of AMD Branch Sampling Stephane Eranian
2021-12-10 21:02 ` [PATCH v4 14/14] perf report: add addr_from/addr_to sort dimensions Stephane Eranian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211210210229.2991238-12-eranian@google.com \
--to=eranian@google.com \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox