From: Wei Li <liwei391@huawei.com>
To: <leo.yan@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>,
"Namhyung Kim" <namhyung@kernel.org>,
Kim Phillips <kim.phillips@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, <guohanjun@huawei.com>
Subject: [PATCH v2 0/2] perf tools: Fix record failure when mixed with ARM SPE event
Date: Fri, 24 Jul 2020 15:11:09 +0800 [thread overview]
Message-ID: <20200724071111.35593-1-liwei391@huawei.com> (raw)
v1 -> v2:
- Optimize code in patch 1 as Mathieu adviced.
- Fix memleak in patch 2.
- Detail the commit info to explain the reason.
This patch set fixes perf record failure when we mix arm_spe_x event
with other events in specific order.
Wei Li (2):
perf tools: Fix record failure when mixed with ARM SPE event
perf tools: ARM SPE code cleanup
tools/perf/arch/arm/util/auxtrace.c | 17 ++++++++---------
1 file changed, 8 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-24 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 7:11 Wei Li [this message]
2020-07-24 7:11 ` [PATCH v2 1/2] " Wei Li
2020-07-24 8:59 ` Leo Yan
2020-07-27 20:29 ` Mathieu Poirier
2020-07-24 7:11 ` [PATCH v2 2/2] perf tools: ARM SPE code cleanup Wei Li
2020-07-27 20:34 ` Mathieu Poirier
2020-07-28 11:42 ` Arnaldo Carvalho de Melo
2020-07-28 12:02 ` Arnaldo Carvalho de Melo
2020-07-28 12:38 ` Leo Yan
2020-07-28 15:46 ` Mathieu Poirier
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=20200724071111.35593-1-liwei391@huawei.com \
--to=liwei391@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=guohanjun@huawei.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®