PRT.DevelopPerformanceCounters History

Hide minor edits - Show changes to markup - Cancel

November 08, 2012, at 03:08 AM by 24.130.186.152 -
Changed line 3 from:

Performance counters can be accessed in multiple ways, normally through a higher-level tool. For This work, we chose to directly use Linux's built-in performance counter calls, which we place at strategic locations in the source code of VMS. The reasons for this choice and details of how to use the calls is in the attached PDF Δ. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel. The PDF should be read before trying to use the visualization system, in order to understand what can go wrong.

to:

Performance counters can be accessed in multiple ways, normally through a higher-level tool. For This work, we chose to directly use Linux's built-in performance counter calls, which we place at strategic locations in the source code of VMS. The reasons for this choice and details of how to use the calls is in the perf_event usage. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel. The PDF should be read before trying to use the visualization system, in order to understand what can go wrong.

November 08, 2012, at 03:03 AM by 24.130.186.152 -
Changed line 14 from:

To check the perf_event_paranoid file, execute: cat /proc/sys/kernel/perf_event_paranoid (it should print out "1"). To change it, you need root priveleges, then just use vi or any other text editor, and put a "1" all by itself on the first line of the file.

to:

To check the perf_event_paranoid file, execute: cat /proc/sys/kernel/perf_event_paranoid (it should print out "-1"). To change it, you need root priveleges, then just use vi or any other text editor, and put a "-1" all by itself on the first line of the file.

November 08, 2012, at 02:47 AM by 24.130.186.152 -
Changed line 3 from:

Performance counters can be accessed in multiple ways, normally through a higher-level tool. For This work, we chose to directly use Linux's built-in performance counter calls, which we place at strategic locations in the source code of VMS. The reasons for this choice and details of how to use the calls is in the attached PDF Δ. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel. The PDF should be read before trying to use the visualization system.

to:

Performance counters can be accessed in multiple ways, normally through a higher-level tool. For This work, we chose to directly use Linux's built-in performance counter calls, which we place at strategic locations in the source code of VMS. The reasons for this choice and details of how to use the calls is in the attached PDF Δ. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel. The PDF should be read before trying to use the visualization system, in order to understand what can go wrong.

November 08, 2012, at 01:56 AM by 24.130.186.152 -
Changed line 18 from:
  • high level page on perf counter usage
to:
  • high level page on perf counter usage
November 08, 2012, at 01:54 AM by 24.130.186.152 -
November 08, 2012, at 01:54 AM by 24.130.186.152 -
Changed lines 19-20 from:
to:
November 08, 2012, at 01:38 AM by 24.130.186.152 -
Changed line 14 from:

To check the perf_event_paranoid file execute: cat /proc/sys/kernel/perf_event_paranoid (it should print out "1")

to:

To check the perf_event_paranoid file, execute: cat /proc/sys/kernel/perf_event_paranoid (it should print out "1"). To change it, you need root priveleges, then just use vi or any other text editor, and put a "1" all by itself on the first line of the file.

November 08, 2012, at 01:35 AM by 24.130.186.152 -
Changed lines 7-8 from:
  • /proc/sys/kernel/perf_event_paranoid must contain 1 (for access by non-privileged users -- the most common reason the calls fail)
to:
  • /proc/sys/kernel/perf_event_paranoid must contain 1 (the most common reason the calls fail)
Changed line 20 from:
to:
November 08, 2012, at 01:33 AM by 24.130.186.152 -
Changed line 11 from:
  • execute this to check the switch: cat /boot/config-<uname output> | grep CONFIG_PERF_COUNTERS
to:
  • execute this to check the switch: cat /boot/config-uname output | grep CONFIG_PERF_COUNTERS
November 08, 2012, at 01:33 AM by 24.130.186.152 -
Changed line 11 from:
  • execute this to check the switch: cat /boot/config-<uname output> | grep CONFIG_PERF_COUNTERS
to:
  • execute this to check the switch: cat /boot/config-<uname output> | grep CONFIG_PERF_COUNTERS
November 08, 2012, at 01:33 AM by 24.130.186.152 -
Changed line 11 from:
  • execute this to check the switch: cat /boot/config-<uname release> | grep CONFIG_PERF_COUNTERS
to:
  • execute this to check the switch: cat /boot/config-<uname output> | grep CONFIG_PERF_COUNTERS
November 08, 2012, at 01:32 AM by 24.130.186.152 -
Added lines 8-14:

To check the CONFIG_PERF_COUNTERS compiler switch,

  • execute uname -r to print the kernel release and look for the corresponding config file in the /boot directory
  • execute this to check the switch: cat /boot/config-<uname release> | grep CONFIG_PERF_COUNTERS
  • It may also work to do this: gzip -cd /proc/config.gz | grep CONFIG_PERF_COUNTERS

To check the perf_event_paranoid file execute: cat /proc/sys/kernel/perf_event_paranoid (it should print out "1")

November 08, 2012, at 01:19 AM by 24.130.186.152 -
Changed lines 3-4 from:

The attached PDF Δ says how to enable performance counters on Linux, and how to put performance counters directly into source code. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel. The PDF should be read before trying to use the visualization system.

to:

Performance counters can be accessed in multiple ways, normally through a higher-level tool. For This work, we chose to directly use Linux's built-in performance counter calls, which we place at strategic locations in the source code of VMS. The reasons for this choice and details of how to use the calls is in the attached PDF Δ. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel. The PDF should be read before trying to use the visualization system.

Changed lines 6-7 from:
  • Kernel has to be compiled with CONFIG_PERF_COUNTERS=y
  • /proc/sys/kernel/perf_event_paranoid must contain 1 (for access by non-privileged users)
to:
  • Kernel has to be compiled with CONFIG_PERF_COUNTERS=y (which is the default for recent kernels)
  • /proc/sys/kernel/perf_event_paranoid must contain 1 (for access by non-privileged users -- the most common reason the calls fail)
November 08, 2012, at 01:14 AM by 24.130.186.152 -
Changed lines 5-7 from:

Here is a page kept by a developer on the PAPI project. It has a fairly complete discussion of all things related to Linux performance counter usage:

  • high level page on perf counter page
to:

The most common reason for perf counters not working are:

  • Kernel has to be compiled with CONFIG_PERF_COUNTERS=y
  • /proc/sys/kernel/perf_event_paranoid must contain 1 (for access by non-privileged users)

Here are some pages from a site by a developer on the PAPI project. The site has a fairly complete discussion of all things related to Linux performance counter usage:

  • high level page on perf counter usage
Changed line 13 from:
to:
November 07, 2012, at 06:34 PM by 24.130.186.152 -
Changed line 3 from:

The attached PDF Δ talks about how to put performance counters directly into source code. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel.

to:

The attached PDF Δ says how to enable performance counters on Linux, and how to put performance counters directly into source code. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel. The PDF should be read before trying to use the visualization system.

September 10, 2012, at 03:57 AM by 24.130.186.152 -
Changed line 8 from:
  • page on low-level perf counter usage
to:
  • page on low-level perf counter usage
Deleted line 9:
September 10, 2012, at 03:57 AM by 24.130.186.152 -
Changed lines 7-8 from:
  • top level page on perf counter page
  • man page on low-level perf counter usage
to:
  • high level page on perf counter page
  • page on low-level perf counter usage
September 10, 2012, at 03:56 AM by 24.130.186.152 -
September 10, 2012, at 03:56 AM by 24.130.186.152 -
Changed line 7 from:
  • main perf counter page
to:
  • top level page on perf counter page
September 10, 2012, at 03:43 AM by 24.130.186.152 -
Added lines 4-10:

Here is a page kept by a developer on the PAPI project. It has a fairly complete discussion of all things related to Linux performance counter usage:

June 30, 2012, at 05:53 AM by 24.130.186.152 -
Changed line 3 from:

The attached PDF talks about how to put performance counters directly into source code. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel.

to:

The attached PDF Δ talks about how to put performance counters directly into source code. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel.

June 30, 2012, at 04:28 AM by 24.130.186.152 -
Added lines 1-3:

Performance Counter Usage

The attached PDF talks about how to put performance counters directly into source code. It references this design document from the Linux source tree: Design document describing the details of performance counters in the Linux kernel.