All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Mike Leach <mike.leach@linaro.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.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>,
	Coresight ML <coresight@lists.linaro.org>,
	Robert Walker <robert.walker@arm.com>
Subject: Re: [PATCH v1 0/4] perf cs-etm: Fix synthesizing instruction samples
Date: Fri, 1 Nov 2019 10:10:55 +0800	[thread overview]
Message-ID: <20191101021055.GA26019@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <CANLsYkzaB2kU20ibuDJVokYeEEuR8wd7MoHzX9+UKnM0jNV1Jg@mail.gmail.com>

On Thu, Oct 31, 2019 at 11:14:15AM -0600, Mathieu Poirier wrote:
> On Thu, 24 Oct 2019 at 09:15, Leo Yan <leo.yan@linaro.org> wrote:
> >
> > This patch series is to address the issue for synthesizing instruction
> > samples, especially when the instruction sample period is small enough,
> > the current logic cannot synthesize multiple instruction samples within
> > one instruction range packet.
> >
> > To fix this issue, patch 0001 avoids to reset the last branches for
> > every instruction sample; if reset the last branches when every time
> > generate instruction sample, then the later samples in the same range
> > packet cannot use the last branches anymore.
> >
> > Patch 0002 is the main patch to fix the logic for synthesizing
> > instruction samples; it allows to handle different instruction periods.
> >
> > Patch 0003 is an optimization for copying last branches; it only copies
> > last branches once if the instruction samples share the same last
> > branches.
> >
> > Patch 0004 is a minor fix for unsigned variable comparison to zero.
> >
> > To verify my changing for synthesizing instruction samples, I added
> > some logs in the code, and reviewed the output log manually for
> > instuctions samples.  The below commands are tested on DB410c board:
> >
> >   # perf script --itrace=i2
> >   # perf script --itrace=i2li16
> >   # perf inject --itrace=i2il16 -i perf.data -o perf.data.new
> >   # perf inject --itrace=i100il16 -i perf.data -o perf.data.new
> >
> >
> > Leo Yan (4):
> >   perf cs-etm: Continuously record last branches
> >   perf cs-etm: Correct synthesizing instruction samples
> >   perf cs-etm: Optimize copying last branches
> >   perf cs-etm: Fix unsigned variable comparison to zero
> 
> I have reviewed and agree with the changes in this set but won't move
> forward until Mike has looked at patch 2/4.

Thanks a lot for reviewing, Mathieu.

Sorry I forgot to loop Mike in this patch set, and respin patch for v2
and have sent to mailing list.  @Mike, please review patch set v2 as
you received, Thanks!

Thanks,
Leo Yan

WARNING: multiple messages have this Message-ID (diff)
From: Leo Yan <leo.yan@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Mike Leach <mike.leach@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Coresight ML <coresight@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Robert Walker <robert.walker@arm.com>,
	Jiri Olsa <jolsa@redhat.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v1 0/4] perf cs-etm: Fix synthesizing instruction samples
Date: Fri, 1 Nov 2019 10:10:55 +0800	[thread overview]
Message-ID: <20191101021055.GA26019@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <CANLsYkzaB2kU20ibuDJVokYeEEuR8wd7MoHzX9+UKnM0jNV1Jg@mail.gmail.com>

On Thu, Oct 31, 2019 at 11:14:15AM -0600, Mathieu Poirier wrote:
> On Thu, 24 Oct 2019 at 09:15, Leo Yan <leo.yan@linaro.org> wrote:
> >
> > This patch series is to address the issue for synthesizing instruction
> > samples, especially when the instruction sample period is small enough,
> > the current logic cannot synthesize multiple instruction samples within
> > one instruction range packet.
> >
> > To fix this issue, patch 0001 avoids to reset the last branches for
> > every instruction sample; if reset the last branches when every time
> > generate instruction sample, then the later samples in the same range
> > packet cannot use the last branches anymore.
> >
> > Patch 0002 is the main patch to fix the logic for synthesizing
> > instruction samples; it allows to handle different instruction periods.
> >
> > Patch 0003 is an optimization for copying last branches; it only copies
> > last branches once if the instruction samples share the same last
> > branches.
> >
> > Patch 0004 is a minor fix for unsigned variable comparison to zero.
> >
> > To verify my changing for synthesizing instruction samples, I added
> > some logs in the code, and reviewed the output log manually for
> > instuctions samples.  The below commands are tested on DB410c board:
> >
> >   # perf script --itrace=i2
> >   # perf script --itrace=i2li16
> >   # perf inject --itrace=i2il16 -i perf.data -o perf.data.new
> >   # perf inject --itrace=i100il16 -i perf.data -o perf.data.new
> >
> >
> > Leo Yan (4):
> >   perf cs-etm: Continuously record last branches
> >   perf cs-etm: Correct synthesizing instruction samples
> >   perf cs-etm: Optimize copying last branches
> >   perf cs-etm: Fix unsigned variable comparison to zero
> 
> I have reviewed and agree with the changes in this set but won't move
> forward until Mike has looked at patch 2/4.

Thanks a lot for reviewing, Mathieu.

Sorry I forgot to loop Mike in this patch set, and respin patch for v2
and have sent to mailing list.  @Mike, please review patch set v2 as
you received, Thanks!

Thanks,
Leo Yan

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-11-01  2:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 15:13 [PATCH v1 0/4] perf cs-etm: Fix synthesizing instruction samples Leo Yan
2019-10-24 15:13 ` Leo Yan
2019-10-24 15:13 ` [PATCH v1 1/4] perf cs-etm: Continuously record last branches Leo Yan
2019-10-24 15:13   ` Leo Yan
2019-10-24 15:13 ` [PATCH v1 2/4] perf cs-etm: Correct synthesizing instruction samples Leo Yan
2019-10-24 15:13   ` Leo Yan
2019-10-24 15:13 ` [PATCH v1 3/4] perf cs-etm: Optimize copying last branches Leo Yan
2019-10-24 15:13   ` Leo Yan
2019-10-24 15:13 ` [PATCH v1 4/4] perf cs-etm: Fix unsigned variable comparison to zero Leo Yan
2019-10-24 15:13   ` Leo Yan
2019-10-31 17:14 ` [PATCH v1 0/4] perf cs-etm: Fix synthesizing instruction samples Mathieu Poirier
2019-10-31 17:14   ` Mathieu Poirier
2019-11-01  2:10   ` Leo Yan [this message]
2019-11-01  2:10     ` 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=20191101021055.GA26019@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=coresight@lists.linaro.org \
    --cc=jolsa@redhat.com \
    --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=robert.walker@arm.com \
    --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 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.