summaryrefslogtreecommitdiffstats
path: root/meta-yocto/conf
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2012-08-31 00:06:57 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-02 05:52:13 -0700
commit17b97774c2069015f6eec6736cace3271ab6b82a (patch)
tree161f1eaa3b143962efc98da9258ad4f6c2aa60b8 /meta-yocto/conf
parent0f9820f9753400d7e9b588921cb394129282af18 (diff)
downloadpoky-17b97774c2069015f6eec6736cace3271ab6b82a.tar.gz
crosstap: new script
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. (From OE-Core rev: c6da6b648328377ba3590fd38cb12dad26a46a13) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto/conf')
0 files changed, 0 insertions, 0 deletions