aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/crosstap
AgeCommit message (Collapse)Author
2013-02-05crosstap: handle hyphenated x86_64 target archTom Zanussi
systemtap_target_arch() should also translate x86-64 (hyphenated) into x86_64 for the -a param. Failing to do that causes systemtap to see an architecture mismatch and create a cloned session with a bogusly synthesized build directory path, and fails to compile the probe. Fixes [YOCTO #3756] Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-02crosstap: new scriptTom Zanussi
This script makes it easy to run a systemtap script on a remote target from a build host. The script itself contains documentation on basic setup and usage - see that for details. In a nutshell, if you have a systemtap script on the build host, this script allows that systemtap script to be compiled and run on the target host and for the output appear on the host terminal. The crosstap script requires to an sdk build of the target (or a build with 'tools-profile' added to EXTRA_IMAGE_FEATURES) because it needs to be able to run the native systemtap built by the systemtap recipe, which in turn needs access to the kernel built for the target in order to build the kernel modules that implement the systemtap probe specified by the systemtap script and which ultimately get shipped to the target and insmod'ed there. The crosstap script also needs to be able to ssh to the target host in order insert the modules on the target, so the target system needs to support incoming ssh connections. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>