From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] perf tools: inject capabilitity for CoreSight traces
Date: Thu, 15 Feb 2018 11:58:33 -0300 [thread overview]
Message-ID: <20180215145833.GF30974@kernel.org> (raw)
In-Reply-To: <CANLsYkz7c7vTFn3M17-=57C__yxcXbTyRLjgjLVBDvoQm6RV7w@mail.gmail.com>
Em Tue, Feb 13, 2018 at 03:18:02PM -0700, Mathieu Poirier escreveu:
> On 7 February 2018 at 06:57, Robert Walker <robert.walker@arm.com> wrote:
> > Added user space perf functionality to translate CoreSight traces into
> > instruction events with branch stack.
> >
> > To invoke the new functionality, use the perf inject
> > tool with --itrace=il. For example, to translate the ETM trace from
> > perf.data into last branch records in a new inj.data file:
> >
> > $ perf inject --itrace=i100000il128 -i perf.data -o perf.data.new
> >
> > The 'i' parameter to itrace generates periodic instruction events. The
> > period between instruction events can be specified as a number of
> > instructions suffixed by i (default 100000).
> > The parameter to 'l' specifies the number of entries in the branch stack
> > attached to instruction events.
> > The 'b' parameter to itrace generates events on taken branches.
> >
> > This patch also fixes the contents of the branch events used in perf report
> > - previously branch events were generated for each contiguous range of
> > instructions executed. These are fixed to generate branch events between
> > the last address of a range ending in an executed branch instruction and
> > the start address of the next range.
> >
> > Based on patches by Sebastian Pop <s.pop@samsung.com> with additional fixes
> > and support for specifying the instruction period.
> >
> > Originally-by: Sebastian Pop <s.pop@samsung.com>
> > Signed-off-by: Robert Walker <robert.walker@arm.com>
>
> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org>
>
> Arnaldo - this should probably go through your tree but let me know if
> you want to proceed otherwise.
I can pick it, but now I'm waiting for Robert to address your comments,
so haven't processed none of these two.
- Arnaldo
> Robert - the work in coresight.txt should likely be published on its
> own. That way Arnaldo doesn't have to worry about it.
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Robert Walker <robert.walker@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org
Subject: Re: [PATCH 1/2] perf tools: inject capabilitity for CoreSight traces
Date: Thu, 15 Feb 2018 11:58:33 -0300 [thread overview]
Message-ID: <20180215145833.GF30974@kernel.org> (raw)
In-Reply-To: <CANLsYkz7c7vTFn3M17-=57C__yxcXbTyRLjgjLVBDvoQm6RV7w@mail.gmail.com>
Em Tue, Feb 13, 2018 at 03:18:02PM -0700, Mathieu Poirier escreveu:
> On 7 February 2018 at 06:57, Robert Walker <robert.walker@arm.com> wrote:
> > Added user space perf functionality to translate CoreSight traces into
> > instruction events with branch stack.
> >
> > To invoke the new functionality, use the perf inject
> > tool with --itrace=il. For example, to translate the ETM trace from
> > perf.data into last branch records in a new inj.data file:
> >
> > $ perf inject --itrace=i100000il128 -i perf.data -o perf.data.new
> >
> > The 'i' parameter to itrace generates periodic instruction events. The
> > period between instruction events can be specified as a number of
> > instructions suffixed by i (default 100000).
> > The parameter to 'l' specifies the number of entries in the branch stack
> > attached to instruction events.
> > The 'b' parameter to itrace generates events on taken branches.
> >
> > This patch also fixes the contents of the branch events used in perf report
> > - previously branch events were generated for each contiguous range of
> > instructions executed. These are fixed to generate branch events between
> > the last address of a range ending in an executed branch instruction and
> > the start address of the next range.
> >
> > Based on patches by Sebastian Pop <s.pop@samsung.com> with additional fixes
> > and support for specifying the instruction period.
> >
> > Originally-by: Sebastian Pop <s.pop@samsung.com>
> > Signed-off-by: Robert Walker <robert.walker@arm.com>
>
> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org>
>
> Arnaldo - this should probably go through your tree but let me know if
> you want to proceed otherwise.
I can pick it, but now I'm waiting for Robert to address your comments,
so haven't processed none of these two.
- Arnaldo
> Robert - the work in coresight.txt should likely be published on its
> own. That way Arnaldo doesn't have to worry about it.
next prev parent reply other threads:[~2018-02-15 14:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 13:57 [PATCH 0/2] Perf inject for ETM trace Robert Walker
2018-02-07 13:57 ` Robert Walker
2018-02-07 13:57 ` [PATCH 1/2] perf tools: inject capabilitity for CoreSight traces Robert Walker
2018-02-07 13:57 ` Robert Walker
2018-02-13 22:18 ` Mathieu Poirier
2018-02-13 22:18 ` Mathieu Poirier
2018-02-15 14:58 ` Arnaldo Carvalho de Melo [this message]
2018-02-15 14:58 ` Arnaldo Carvalho de Melo
2018-02-07 13:57 ` [PATCH 2/2] perf inject: Emit instruction records on ETM trace discontinuity Robert Walker
2018-02-07 13:57 ` Robert Walker
2018-02-13 22:22 ` Mathieu Poirier
2018-02-13 22:22 ` Mathieu Poirier
2018-02-15 14:57 ` Arnaldo Carvalho de Melo
2018-02-15 14:57 ` Arnaldo Carvalho de Melo
2018-02-15 15:22 ` Robert Walker
2018-02-15 15:22 ` Robert Walker
2018-02-15 17:08 ` 'Arnaldo Carvalho de Melo'
2018-02-15 17:08 ` 'Arnaldo Carvalho de Melo'
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=20180215145833.GF30974@kernel.org \
--to=acme@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.