linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kim.phillips@arm.com (Kim Phillips)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] perf: Add ioctl for PMU driver configuration
Date: Fri, 6 Jul 2018 18:38:44 -0500	[thread overview]
Message-ID: <20180706183844.9de52f1d45e1775b51790e8e@arm.com> (raw)
In-Reply-To: <1530828827-11604-1-git-send-email-mathieu.poirier@linaro.org>

On Thu,  5 Jul 2018 16:13:40 -0600
Mathieu Poirier <mathieu.poirier@linaro.org> wrote:

> This set adds the capability to communiate event specific configuration
> to the PMU kernel driver using an ioctl().  The functionatlity is made
> generic enough for anyone to use but is targeted at the identification
> of CoreSight sinks when operating in CPU-wide trace scenarios.

With this series, a --per-thread -less invocation looks like it
succeeds (instead of giving a "failed to mmap with 12 (Cannot allocate
memory)" error):

# perf record -e /cs_etm/@20010000.etf/ sleep 1
[ perf record: Woken up 3 times to write data ]
Warning:
AUX data lost 2 times out of 3!

[ perf record: Captured and wrote 0.182 MB perf.data ]
# 

but now perf report - built with libopencsd - is unable to process the
perf.data file:

# perf report --stdio 
0x3a0 [0x60]: failed to process type: 1
Error:
failed to process sample
# To display the perf.data header info, please use --header/--header-only options.
#

Also, a "record -a" invocation also acts like it's working, but Juno
has a hardware limitation where it can't record all cpus concurrently,
right?  So, shouldn't record commands that exceed the h/w's
capabilities error out instead?

Thanks,

Kim

  parent reply	other threads:[~2018-07-06 23:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05 22:13 [PATCH v2 0/7] perf: Add ioctl for PMU driver configuration Mathieu Poirier
2018-07-05 22:13 ` [PATCH v2 1/7] perf: Introduce ioctl to communicate driver configuration to kernel Mathieu Poirier
2018-07-05 22:13 ` [PATCH v2 2/7] perf/core: Use " Mathieu Poirier
2018-07-06 23:22   ` Kim Phillips
2018-07-09 16:49     ` Mathieu Poirier
2018-07-09 21:45       ` Mathieu Poirier
2018-07-05 22:13 ` [PATCH v2 3/7] perf/aux: Make perf_event accessible to setup_aux() Mathieu Poirier
2018-07-05 22:13 ` [PATCH v2 4/7] coresight: Use PMU driver configuration for sink selection Mathieu Poirier
2018-07-05 22:13 ` [PATCH v2 5/7] perf tools: Use ioctl to communicate driver configuration to kernel Mathieu Poirier
2018-07-05 22:13 ` [PATCH v2 6/7] perf tools: Make perf_evsel accessible to PMU driver configuration code Mathieu Poirier
2018-07-05 22:13 ` [PATCH v2 7/7] perf tools: Use ioctl function to send sink configuration to kernel Mathieu Poirier
2018-07-06 23:38 ` Kim Phillips [this message]
2018-07-09 19:21   ` [PATCH v2 0/7] perf: Add ioctl for PMU driver configuration 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=20180706183844.9de52f1d45e1775b51790e8e@arm.com \
    --to=kim.phillips@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).