linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: adrienverge@gmail.com (Adrien Vergé)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/6] ARM CoreSight: Enhance ETM tracing control
Date: Fri, 24 Jan 2014 11:40:50 -0500	[thread overview]
Message-ID: <1390581656-16372-1-git-send-email-adrienverge@gmail.com> (raw)

Hi,

Different ARM users have shown their interest in this patch, so I made
a second version that corrects the first mistakes.

Mainly, it extends current support of CoreSight ETM, that is currently
very limited. ETM provides hardware-assisted program tracing, a
cycle-precise and low-overhead solution that software tools such as
'perf record' cannot provide.

Usage of ETM tracing facility is presently limited to start and stop
tracing. This set of patches enables management of address combinations
and PIDs that trigger tracing, thus allowing to trace specific
functions and processes.

ETM management was done via sysfs entries (trace_info,
trace_running...), this code adds trace_addrrange and trace_pid to
let the user read/write custom values.

Changes in V2:
- Use device attributes rather than raw kobjects
- Make PID_IN_CONTEXTIDR incompatible with PID_NS in Kconfig
- Use int for pid type (not long)
- During trace fetching, call vmalloc() only if really needed

This series of patches applies to v3.13.

Adrien Verg? (6):
  ARM CoreSight: ETM: Use device attributes
  ARM CoreSight: ETM: Rename 'comparator' to 'address comparator'
  ARM CoreSight: ETM: Add address control support
  ARM: Make PID_IN_CONTEXTIDR incompatible with PID_NS
  ARM CoreSight: ETM: Add PID control support
  ARM CoreSight: ETM: Allocate a trace buffer only when necessary

 arch/arm/Kconfig.debug                    |   2 +-
 arch/arm/include/asm/hardware/coresight.h |   9 +-
 arch/arm/kernel/etm.c                     | 208 +++++++++++++++++++++++-------
 arch/arm64/Kconfig.debug                  |   1 +
 4 files changed, 169 insertions(+), 51 deletions(-)

-- 
1.8.5.2

             reply	other threads:[~2014-01-24 16:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 16:40 Adrien Vergé [this message]
2014-01-24 16:40 ` [PATCH V2 1/6] ARM CoreSight: ETM: Use device attributes Adrien Vergé
2014-01-24 16:40 ` [PATCH V2 2/6] ARM CoreSight: ETM: Rename 'comparator' to 'address comparator' Adrien Vergé
2014-01-24 16:40 ` [PATCH V2 3/6] ARM CoreSight: ETM: Add address control support Adrien Vergé
2014-01-24 16:40 ` [PATCH V2 4/6] ARM: Make PID_IN_CONTEXTIDR incompatible with PID_NS Adrien Vergé
2014-01-24 16:43   ` Will Deacon
2014-01-24 17:16     ` Adrien Vergé
2014-01-24 17:17       ` Will Deacon
2014-01-24 17:52         ` Christopher Covington
2014-01-24 19:12           ` Christopher Covington
2014-01-24 19:34           ` Adrien Vergé
2014-01-24 16:40 ` [PATCH V2 5/6] ARM CoreSight: ETM: Add PID control support Adrien Vergé
2014-01-24 16:40 ` [PATCH V2 6/6] ARM CoreSight: ETM: Allocate a trace buffer only when necessary Adrien Vergé

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=1390581656-16372-1-git-send-email-adrienverge@gmail.com \
    --to=adrienverge@gmail.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).