linux-toradex.git/include/trace, branch tegra-12r8-early

nvhost: Move include files to kernel/include

2011-08-16T00:03:48+00:00

To prepare for kernel modularization, nvhost include files need to be
moved from mach-tegra/include to kernel/include. At the same time
user space specific part is split into nvhost_ioctl.h.

Bug 854182

Change-Id: I3694a40d786028733310ecf5b59341282af571be
Signed-off-by: Terje Bergstrom 
Reviewed-on: http://git-master/r/43211
Reviewed-by: Varun Colbert 
Tested-by: Varun Colbert

tracing, perf: Add more power related events

2011-05-11T22:17:49+00:00

This patch adds new generic events for dynamic power management
tracing:

 - clock events class: used for clock enable/disable and for
   clock rate change,
 - power_domain events class: used for power domains transitions.

The OMAP architecture will be using the new events for PM debugging,
however the new events are made generic enough to be used by all
platforms.

Signed-off-by: Jean Pihet 
Acked-by: Thomas Renninger 
Cc: discuss@lesswatts.org
Cc: linux-pm@lists.linux-foundation.org
Cc: Thomas Renninger 
Cc: Arjan van de Ven 
Cc: Peter Zijlstra 
Cc: Len Brown 
Cc: Kevin Hilman 
LKML-Reference: 
Signed-off-by: Ingo Molnar 
Change-Id: I7e1d1425214f5a90672f423ce882e4337f2d0114
Reviewed-on: http://git-master/r/30383
Reviewed-by: Daniel Willemsen 
Reviewed-by: Peter De Schrijver 
Tested-by: Peter De Schrijver 
Reviewed-by: Aleksandr Frid 
Reviewed-by: Scott Williams

regulator: Add basic trace facilities

2011-05-11T22:17:30+00:00

Provide some basic trace facilities to the regulator API. We generate
events on regulator enable, disable and voltage setting over the actual
hardware operations (which are assumed to be the expensive ones which
require interaction with the actual device). This is intended to facilitate
debug of the performance and behaviour with consumers allowing unified
traces to be generated including the regulator operations within the
context of the other components of the system.

For enable we log the explicit delay for the voltage ramp separately to
the interaction with the hardware to highlight the time consumed in I/O.
We should add a similar delay for voltage changes, though there the
relatively small magnitude of the changes in the context of the I/O
costs makes it much less critical for most regulators.

Only hardware interactions are currently traced as the primary focus is
on the performance and synchronisation of actual hardware interactions.
Additional tracepoints for debugging of the logical operations can be
added later if required.

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood 
Change-Id: I351d02094bad5cfc5454b3b6c90853b714bee182
Reviewed-on: http://git-master/r/30382
Reviewed-by: Daniel Willemsen 
Reviewed-by: Aleksandr Frid 
Reviewed-by: Scott Williams 
Reviewed-by: Narendra Damahe 
Reviewed-by: Peter De Schrijver 
Tested-by: Peter De Schrijver 
Reviewed-by: Yu-Huan Hsu

Merge branch 'perf-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip

2010-08-24T19:21:49+00:00

* 'perf-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
  watchdog: Don't throttle the watchdog
  tracing: Fix timer tracing

workqueue: Add basic tracepoints to track workqueue execution

2010-08-21T20:19:37+00:00

With the introduction of the new unified work queue thread pools,
we lost one feature: It's no longer possible to know which worker
is causing the CPU to wake out of idle. The result is that PowerTOP
now reports a lot of "kworker/a:b" instead of more readable results.

This patch adds a pair of tracepoints to the new workqueue code,
similar in style to the timer/hrtimer tracepoints.

With this pair of tracepoints, the next PowerTOP can correctly
report which work item caused the wakeup (and how long it took):

Interrupt (43)            i915      time   3.51ms    wakeups 141
Work      ieee80211_iface_work      time   0.81ms    wakeups  29
Work              do_dbs_timer      time   0.55ms    wakeups  24
Process                   Xorg      time  21.36ms    wakeups   4
Timer    sched_rt_period_timer      time   0.01ms    wakeups   1

Signed-off-by: Arjan van de Ven 
Signed-off-by: Linus Torvalds

tracing: Fix timer tracing

2010-08-19T11:00:41+00:00

PowerTOP would like to be able to trace timers.

Unfortunately, the current timer tracing is not very useful: the
actual timer function is not recorded in the trace at the start
of timer execution.

Although this is recorded for timer "start" time (when it gets
armed), this is not useful; most timers get started early, and a
tracer like PowerTOP will never see this event, but will only
see the actual running of the  timer.

This patch just adds the function to the timer tracing; I've
verified with PowerTOP that now it can get useful information
about timers.

Signed-off-by: Arjan van de Ven 
Cc: xiaoguangrong@cn.fujitsu.com
Cc: Steven Rostedt 
Cc: Frederic Weisbecker 
Cc: Peter Zijlstra 
Cc:  # .35.x, .34.x, .33.x
LKML-Reference: <4C6C5FA9.3000405@linux.intel.com>
Signed-off-by: Ingo Molnar

Merge branch 'for-2.6.36' of git://git.kernel.dk/linux-2.6-block

2010-08-10T22:22:42+00:00

* 'for-2.6.36' of git://git.kernel.dk/linux-2.6-block: (149 commits)
  block: make sure that REQ_* types are seen even with CONFIG_BLOCK=n
  xen-blkfront: fix missing out label
  blkdev: fix blkdev_issue_zeroout return value
  block: update request stacking methods to support discards
  block: fix missing export of blk_types.h
  writeback: fix bad _bh spinlock nesting
  drbd: revert "delay probes", feature is being re-implemented differently
  drbd: Initialize all members of sync_conf to their defaults [Bugz 315]
  drbd: Disable delay probes for the upcomming release
  writeback: cleanup bdi_register
  writeback: add new tracepoints
  writeback: remove unnecessary init_timer call
  writeback: optimize periodic bdi thread wakeups
  writeback: prevent unnecessary bdi threads wakeups
  writeback: move bdi threads exiting logic to the forker thread
  writeback: restructure bdi forker loop a little
  writeback: move last_active to bdi
  writeback: do not remove bdi from bdi_list
  writeback: simplify bdi code a little
  writeback: do not lose wake-ups in bdi threads
  ...

Fixed up pretty trivial conflicts in drivers/block/virtio_blk.c and
drivers/scsi/scsi_error.c as per Jens.

memcg: add mm_vmscan_memcg_isolate tracepoint

2010-08-10T03:45:03+00:00

Memcg also need to trace page isolation information as global reclaim.
This patch does it.

Signed-off-by: KOSAKI Motohiro 
Reviewed-by: KAMEZAWA Hiroyuki 
Acked-by: Mel Gorman 
Acked-by: Balbir Singh 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

vmscan: convert mm_vmscan_lru_isolate to DEFINE_EVENT

2010-08-10T03:45:03+00:00

Mel Gorman recently added some vmscan tracepoints.  Unfortunately they are
covered only global reclaim.  But we want to trace memcg reclaim too.

Thus, this patch convert them to DEFINE_TRACE macro.  it help to reuse
tracepoint definition for other similar usage (i.e.  memcg).  This patch
have no functionally change.

Signed-off-by: KOSAKI Motohiro 
Reviewed-by: KAMEZAWA Hiroyuki 
Acked-by: Balbir Singh 
Acked-by: Mel Gorman 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

memcg, vmscan: add memcg reclaim tracepoint

2010-08-10T03:45:03+00:00

Memcg also need to trace reclaim progress as direct reclaim.  This patch
add it.

Signed-off-by: KOSAKI Motohiro 
Reviewed-by: KAMEZAWA Hiroyuki 
Acked-by: Mel Gorman 
Acked-by: Balbir Singh 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds