summaryrefslogtreecommitdiffstats
path: root/driver
diff options
context:
space:
mode:
authorPawel Moll2011-11-14 04:46:16 -0600
committerPawel Moll2011-11-17 12:04:47 -0600
commitbdf11fa03c80126715edd12da7196c52034da4f1 (patch)
tree2a56872f3466d6aec1f93944955ff058dbf5ea35 /driver
parent8fc69a3638ca8d08111c161b1487868cb42cd888 (diff)
downloadarm-ds5-gator-bdf11fa03c80126715edd12da7196c52034da4f1.tar.gz
arm-ds5-gator-bdf11fa03c80126715edd12da7196c52034da4f1.tar.xz
arm-ds5-gator-bdf11fa03c80126715edd12da7196c52034da4f1.zip
gator: Move README to top directory
... as it applies to both driver and daemon now. Signed-off-by: Pawel Moll <pawel.moll@arm.com>
Diffstat (limited to 'driver')
-rw-r--r--driver/README_Streamline.txt97
1 files changed, 0 insertions, 97 deletions
diff --git a/driver/README_Streamline.txt b/driver/README_Streamline.txt
deleted file mode 100644
index 9b64b8e..0000000
--- a/driver/README_Streamline.txt
+++ /dev/null
@@ -1,97 +0,0 @@
1
2*** Purpose ***
3
4Instructions on setting up ARM Streamline on the target.
5The gator driver and gator daemon are required to run on the ARM linux target in order for ARM Streamline to operate.
6The driver should be built as a module and the daemon must run with root permissions on the target.
7
8*** Introduction ***
9
10A linux development environment with cross compiling tools is most likely required, depending on what is already created and provided.
11-For users, the ideal environment is to be given a BSP with gatord and gator.ko already running on a properly configured kernel. In such a scenario, a development environment is not needed, root permission may or may not be needed (gatord must be executed with root permissions but can be automatically started, see below), and the user can run Streamline and profile the system without any setup.
12-The ideal development environment has the kernel source code available to be rebuilt and executed on the target. This environment allows the greatest flexibility in configuring the kernel and building the gator driver module.
13-However, it is possible that a user/developer has a kernel but does not have the source code. In this scenario it may or may not be possible to obtain a valid profile.
14 -First, check if the kernel has the proper configuration options (see below). Profiling cannot occur using a kernel that is not configured properly, a new kernel must be created.
15 -Second, given a properly configured kernel, check if the filesystem contains the kernel source/headers, which can be used to re-create the gator driver.
16 -If the kernel is not properly configured or sources/headers are not available, the developer is on their own and kernel creation is beyond the scope of this document. Note: It is possible for a module to work when compiled against a similar kernel source code, though this is not guaranteed to work due to differences in kernel structures, exported symbols and incompatible configuration parameters.
17
18*** Preparing and building the kernel ***
19
20cd into the root source dir of the linux kernel
21if your target has never been configured, choose the appropriate configuration for your target
22 make ARCH=arm CROSS_COMPILE=${CROSS_TOOLS}/bin/arm-none-linux-gnueabi- <platform_defconfig>
23make ARCH=arm CROSS_COMPILE=${CROSS_TOOLS}/bin/arm-none-linux-gnueabi- menuconfig
24
25Required Kernel Changes (depending on the kernel version, the location of these configuration settings within menuconfig may be different)
26- General Setup
27 - [*] Profiling Support
28- Kernel hacking
29 - [*] Tracers
30 - [*] Trace process context switches and events
31- Kernel Features
32 - [*] High Resolution Timer Support
33 - [*] Use local timer interrupts (only required for SMP)
34
35The "context switches and events" option will not be available if other trace configurations are enabled. Other trace configurations being enabled is sufficient to turn on context switches and events.
36
37Optional Kernel Changes (depending on the kernel version, the location of these configuration settings within menuconfig may be different)
38Note: Configurations may not be supported on all targets
39- System Type
40 - [*] <SoC name> debugging peripherals (enable core performance counters on supported SoCs) /* kernels before 2.6.35 */
41
42make -j5 ARCH=arm CROSS_COMPILE=${CROSS_TOOLS}/bin/arm-none-linux-gnueabi- uImage
43
44*** Checking the gator requirements ***
45
46(optional) Use the hrtimer_module utility to validate the kernel High Resolution Timer requirement.
47
48*** Building the gator module ***
49
50To create the gator.ko module,
51 cd /ds-5-install-directory/arm/gator/driver-src
52 tar xzf gator-driver.tar.gz
53 cd gator-driver
54 make -C <kernel_build_dir> M=`pwd` ARCH=arm CROSS_COMPILE=<...> modules
55for example
56 make -C /home/username/kernel_2.6.32/ M=`pwd` ARCH=arm CROSS_COMPILE=/home/username/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi- modules
57If successful, a gator.ko module should be generated
58
59*** Compiling an application or shared library ***
60
61Recommended compiler settings:
62 "-g": Debug symbols needed for best analysis results.
63 "-fno-inline": Speed improvement when processing the image files and most accurate analysis results.
64 "-fno-omit-frame-pointer": ARM EABI frame pointers (Code Sourcery cross compiler) allow the call stack to be recorded with each sample taken when in ARM state (i.e. not -mthumb).
65
66*** Running gator ***
67
68Load the kernel onto the target and copy gatord and gator.ko into the target's filesystem.
69gatord is located in <installdir>/arm/gator/linux or <installdir>/arm/gator/android or can be built from source.
70Ensure gatord has execute permissions
71 chmod +x gatord
72gator.ko must be located in the same directory as gatord on the target.
73With root privileges, run the daemon
74 sudo ./gatord &
75
76*** Profiling the kernel (optional) ***
77
78make ARCH=arm CROSS_COMPILE=$(CROSS_TOOLS}/bin/arm-none-linux-gnueabi- menuconfig
79- Kernel Hacking
80 - [*] Compile the kernel with debug info
81
82make -j5 ARCH=arm CROSS_COMPILE=${CROSS_TOOLS}/bin/arm-none-linux-gnueabi- uImage
83Use vmlinux as the image for debug symbols in Streamline.
84Drivers may be profiled using this method by statically linking the driver into the kernel image or adding the module as an image.
85Note that the gator driver does not perform kernel call stack recording.
86
87*** Automatically start gator on boot (optional) ***
88
89cd /etc/init.d
90vi rungator.sh
91 #!/bin/bash
92 /path/to/gatord &
93update-rc.d rungator.sh defaults
94
95*** GPL License ***
96
97For license information, please see the file LICENSE after unzipping driver-src/gator-driver.tar.gz.