public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Cc: suzuki.poulose@arm.com, alexander.shishkin@linux.intel.com,
	coresight@lists.linaro.org, acme@kernel.org,
	peterz@infradead.org, mingo@redhat.com, leo.yan@linaro.org,
	mike.leach@linaro.org
Subject: [PATCH V2 0/6] coresight: Fix snapshot mode
Date: Tue, 14 May 2019 13:40:12 -0600	[thread overview]
Message-ID: <20190514194018.23420-1-mathieu.poirier@linaro.org> (raw)

This is the second revision of a set that fix miscellaneous problems
preventing snapshot mode from working properly when CoreSight events are
used.

It applies cleanly on the coresight next branch[1] and will be posted
again when 5.2-rc1 comes out.

Best regards,
Mathieu

[1]. https://git.linaro.org/kernel/coresight.git/ branch next

Changes for V2:
* Drop requirement to make the perf AUX buffer the same size as the sink
  buffers.
* Re-worked the user space algorithm to find '*head' and '*old".
* Fixed typo in changelogs (Leo).

Mathieu Poirier (6):
  coresight: etb10: Properly set AUX buffer head in snapshot mode
  coresight: tmc-etr: Properly set AUX buffer head in snapshot mode
  coresight: tmc-etf: Properly set AUX buffer head in snapshot mode
  coresight: tmc-etf: Fix snapshot mode update function
  coresight: perf: Don't set the truncated flag in snapshot mode
  perf tools: Properly set the value of 'old' and 'head' in snapshot
    mode

 drivers/hwtracing/coresight/coresight-etb10.c |  21 ++-
 .../hwtracing/coresight/coresight-tmc-etf.c   |  28 ++--
 .../hwtracing/coresight/coresight-tmc-etr.c   |  19 ++-
 tools/perf/arch/arm/util/cs-etm.c             | 124 +++++++++++++++++-
 4 files changed, 165 insertions(+), 27 deletions(-)

-- 
2.17.1


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

             reply	other threads:[~2019-05-14 19:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 19:40 Mathieu Poirier [this message]
2019-05-14 19:40 ` [PATCH V2 1/6] coresight: etb10: Properly set AUX buffer head in snapshot mode Mathieu Poirier
2019-05-15  9:45   ` Suzuki K Poulose
2019-05-15 14:28     ` Mathieu Poirier
2019-05-16  9:41       ` Suzuki K Poulose
2019-05-14 19:40 ` [PATCH V2 2/6] coresight: tmc-etr: " Mathieu Poirier
2019-05-14 19:40 ` [PATCH V2 3/6] coresight: tmc-etf: " Mathieu Poirier
2019-05-14 19:40 ` [PATCH V2 4/6] coresight: tmc-etf: Fix snapshot mode update function Mathieu Poirier
2019-05-14 19:40 ` [PATCH V2 5/6] coresight: perf: Don't set the truncated flag in snapshot mode Mathieu Poirier
2019-05-16 15:22   ` Suzuki K Poulose
2019-05-14 19:40 ` [PATCH V2 6/6] perf tools: Properly set the value of 'old' and 'head' " Mathieu Poirier
2019-05-16 15:00   ` Leo Yan
2019-05-20 19:53     ` Mathieu Poirier
2019-05-21  1:54       ` Leo Yan
2019-05-16 15:09 ` [PATCH V2 0/6] coresight: Fix " 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=20190514194018.23420-1-mathieu.poirier@linaro.org \
    --to=mathieu.poirier@linaro.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=coresight@lists.linaro.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mike.leach@linaro.org \
    --cc=mingo@redhat.com \
    --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