From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Leo Yan <leo.yan@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Mike Leach <mike.leach@linaro.org>,
Robert Walker <robert.walker@arm.com>,
Kim Phillips <kim.phillips@arm.com>
Subject: Re: [PATCH v1 0/6] perf cs-etm: Fix tracing packet handling and minor refactoring
Date: Tue, 19 Jun 2018 15:19:43 -0300 [thread overview]
Message-ID: <20180619181943.GL20477@kernel.org> (raw)
In-Reply-To: <CANLsYkyxuz+tPrC7wb1omsw+qj=7ZB5t6FRbqZz54994g62q6g@mail.gmail.com>
Em Tue, Jun 19, 2018 at 11:46:02AM -0600, Mathieu Poirier escreveu:
> On Sun, 17 Jun 2018 at 23:10, Leo Yan <leo.yan@linaro.org> wrote:
> >
> > Due the current code is missing to handle cs-etm start tracing packet
> > and CS_ETM_TRACE_ON packet, we fail to generate branch sample for them.
> >
> > This patch series is to fix cs-etm tracing packet handling:
> >
> > Patch 0001 is to add invalid address macro for readable coding;
> >
> > Patch 0002 is one minor fixing to return error code for instruction
> > sample failure;
> >
> > Patches 0003~0006 are fixing patches for start tracing packet
> > and CS_ETM_TRACE_ON packet.
> >
> > This patch series is applied on acme tree [1] on branch perf/core with
> > latest commit: e238cf2e3d2e ("perf intel-pt: Fix packet decoding of CYC
> > packets"). Also applied successfully this patch series on Linus tree
> > on 4.18-rc1.
> >
> > This patch series has been verified on Hikey620 platform with below two
> > commands:
> > perf script --itrace=i10000il128 -F cpu,event,ip,addr,sym -k ./vmlinux
> > perf script -F cpu,event,ip,addr,sym -k ./vmlinux
> >
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> >
> >
> > Leo Yan (6):
> > perf cs-etm: Introduce invalid address macro
> > perf cs-etm: Bail out immediately for instruction sample failure
> > perf cs-etm: Fix start tracing packet handling
> > perf cs-etm: Support dummy address value for CS_ETM_TRACE_ON packet
> > perf cs-etm: Generate branch sample when receiving a CS_ETM_TRACE_ON
> > packet
> > perf cs-etm: Generate branch sample for CS_ETM_TRACE_ON packet
> >
> > tools/perf/util/cs-etm-decoder/cs-etm-decoder.c | 10 ++--
> > tools/perf/util/cs-etm-decoder/cs-etm-decoder.h | 1 +
> > tools/perf/util/cs-etm.c | 71 +++++++++++++++++++++----
> > 3 files changed, 68 insertions(+), 14 deletions(-)
>
> Good day Arnaldo,
>
> I am good with this set:
>
> Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
>
> Please consider for inclusion in your tree if you are satisfied with the work.
I'll take a look and get it into perf/core, now I'm concentrating on
perf/urgent work.
Thanks,
- Arnaldo
next prev parent reply other threads:[~2018-06-19 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 5:09 [PATCH v1 0/6] perf cs-etm: Fix tracing packet handling and minor refactoring Leo Yan
2018-06-18 5:09 ` [PATCH v1 1/6] perf cs-etm: Introduce invalid address macro Leo Yan
2018-07-25 20:40 ` [tip:perf/core] " tip-bot for Leo Yan
2018-06-18 5:09 ` [PATCH v1 2/6] perf cs-etm: Bail out immediately for instruction sample failure Leo Yan
2018-07-25 20:41 ` [tip:perf/core] " tip-bot for Leo Yan
2018-06-18 5:09 ` [PATCH v1 3/6] perf cs-etm: Fix start tracing packet handling Leo Yan
2018-06-18 5:09 ` [PATCH v1 4/6] perf cs-etm: Support dummy address value for CS_ETM_TRACE_ON packet Leo Yan
2018-06-18 5:09 ` [PATCH v1 5/6] perf cs-etm: Generate branch sample when receiving a " Leo Yan
2018-06-18 5:09 ` [PATCH v1 6/6] perf cs-etm: Generate branch sample for " Leo Yan
2018-06-19 17:46 ` [PATCH v1 0/6] perf cs-etm: Fix tracing packet handling and minor refactoring Mathieu Poirier
2018-06-19 18:19 ` Arnaldo Carvalho de Melo [this message]
2018-07-02 2:35 ` leo.yan
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=20180619181943.GL20477@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.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=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robert.walker@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