This directory contains example configs to use ktest for various tasks. The configs still need to be customized for your environment, but it is broken up by task which makes it easier to understand how to set up ktest. The configs are based off of real working configs but have been modified and commented to show more generic use cases that are more helpful for developers. crosstests.conf - this config shows an example of testing a git repo against lots of different architectures. It only does build tests, but makes it easy to compile test different archs. You can download the arch cross compilers from: http://kernel.org/pub/tools/crosstool/files/bin/x86_64/ test.conf - A generic example of a config. This is based on an actual config used to perform real testing. kvm.conf - A example of a config that is used to test a virtual guest running on a host. snowball.conf - An example config that was used to demo ktest.pl against a snowball ARM board. include/ - The include directory holds default configs that can be included into other configs. This is a real use example that shows how to reuse configs for various machines or set ups. The files here are included by other config files, where the other config files define options and variables that will make the included config work for the given environment. m> net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
path: root/tools/arch/sh/include
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-30 19:27:10 -0500
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-31 09:13:49 -0500
commit79c6f448c8b79c321e4a1f31f98194e4f6b6cae7 (patch)
tree370efda701f03cccf21e02bb1fdd3b852547d75c /tools/arch/sh/include
parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/arch/sh/include')