summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* [debian] set distribution=unstable for upload to DebianHEADdebian/1.5-2masterUwe Kleine-König2019-12-081-2/+2
|
* [debian] Fix FTBFS on all but arm32 and x86Uwe Kleine-König2019-12-083-0/+25
|
* [debian] Drop Conflicts: xenomai-runtimeUwe Kleine-König2019-12-062-1/+6
|
* [debian] set distribution=unstable for upload to Debiandebian/1.5-1Uwe Kleine-König2019-12-051-2/+2
|
* [debian] bump debhelper compat level (9 -> 12)Uwe Kleine-König2019-12-053-2/+2
|
* [debian] update d/copyright for new upstream releaseUwe Kleine-König2019-12-051-6/+1
|
* [debian] enable hardeningUwe Kleine-König2019-12-052-0/+2
|
* [debian] new patches applied upstream to fix typos and empty directoriesUwe Kleine-König2019-12-056-12/+84
| | | | This requires a patch refresh.
* [debian] Add bug-closer for python2-removal bugUwe Kleine-König2019-12-051-0/+1
|
* [debian] Update d/watch to use https.Uwe Kleine-König2019-11-172-1/+2
|
* [debian] Don't use .sh suffix for shell scriptsUwe Kleine-König2019-11-152-0/+77
|
* [debian] Depend on python3 instead of pythonUwe Kleine-König2019-11-152-1/+3
|
* [debian] Bump Standards-VersionUwe Kleine-König2019-11-152-1/+2
|
* [debian] move from Priority: extra to Priority: optionalUwe Kleine-König2019-11-152-1/+2
|
* [debian] Update Vcs-URLsUwe Kleine-König2019-11-152-2/+3
| | | | | The hosting server has appropriate forwards, but to not have to rely on these update to the current scheme of URLs.
* [debian] Update d/copyright for 1.5 and fix orderingUwe Kleine-König2019-11-152-6/+10
| | | | | | | The latest matching Files: section is the relevant, so Files: * must come first to not overwrite all previous entries. Also use https-URL and add a file added since 1.0.
* [debian] refresh patches and update version in d/changelogUwe Kleine-König2019-11-158-129/+25
|
* [debian] Merge tag 'v1.5' of ↵Uwe Kleine-König2019-11-1539-1080/+5581
|\ | | | | | | | | | | git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests v1.5
| * rt-tests: Makefile update versionJohn Kacur2019-08-191-1/+1
| | | | | | | | | | | | Update the version in the Makefile to 1.5 Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: cyclictest: Without -t default to 1 thread in numa caseJohn Kacur2019-08-141-7/+4
| | | | | | | | | | | | | | | | | | | | | | Don't ignore -t num when detecting if numa support is available. Also, don't be too smart about details in the case of numa support This means, if -t is not specified then the default is 1. affinity must also be explicily set. Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: hwlatdetect: Remove kmodule options and clean-up helpJohn Kacur2019-08-072-32/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | hwlatdetect has used the ftrace hwlatdetector for quite sometime. When we first moved away from our own kernel module, it was still possible to force the use of the module for testing. This was useful for development but is no longer supported. This patch does the following things. - Remove references to the kmodule from the help option and the man page. - Remove support from the program to force loading of the module. - Cleans up some differences between the manpage and the program help, for example, adds the --hardlimit option to man page and removes the --cleanup of the kmodule option Signed-off-by: John Kacur <jkacur@redhat.com>
| * ptsematest, sigwaittest, pmqtest, svsematest reprot error "Could not access ↵Qiao Zhao2019-07-314-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | /sys/kernel/debug/tracing/tracing_enabled" tracing_enabled was deprecated a long time ago and is no longer available, use tracing_on instead To reproduce This patches fixes that Signed-off-by: Qiao Zhao <qzhao@redhat.com> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: Use gettid from rt-utils.c everywhereJohn Kacur2019-06-267-15/+0
| | | | | | | | | | | | | | | | | | gettid is defined in rt-utils, so we should use that everywhere instead of defining a separate macro in each test for it. Signed-off-by: John Kacur <jkacur@redhat.com> Acked-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Acked-by: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>
| * rt-tests: cyclicdeadline: Fix cgroup setupKurt Kanzenbach2019-06-191-1/+0
| | | | | | | | | | | | | | | | | | | | Deadline tasks cannot be pinned to specific CPUs by using affinities. Cgroups have to be used instead. Cylicdeadline has code to do so. However, that code is never executed, because the all_cpus variable is reassigned after argument parsing. Remove it. Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: cyclicdeadline: Print fail only if something failedKurt Kanzenbach2019-06-191-2/+3
| | | | | | | | | | | | | | | | | | | | | | It is interesting to see what went wrong in case something did. However, the fail statement is printed always. That is confusing. Furthermore, the fail value is always 1 when a failure happened. There is no need to print it. Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: cyclicdeadline: Add options to usageKurt Kanzenbach2019-06-191-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | The current usage doesn't show the available options: $ sudo ./cyclicdeadline -h usage: cyclicdeadline So, add the options to the help text to see what can be configured. Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: deadline: Remove duplicated gettid() codeKurt Kanzenbach2019-06-192-8/+4
| | | | | | | | | | | | | | gettid() is already implemented in the library code. Use that code instead. Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: cyclicdeadline: Remove unused getcpu codeKurt Kanzenbach2019-06-191-11/+0
| | | | | | | | | | | | | | | | The getcpu() system call isn't used in the program. Therefore, it can be removed. Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: deadline: Remove duplicated code for sched_{set,get}_attrKurt Kanzenbach2019-06-192-105/+3
| | | | | | | | | | | | | | | | The system calls for sched_get_attr() and sched_set_attr() are already implemented. Get rid of the code and use the existing libary. Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: Version 1.4John Kacur2019-06-191-1/+1
| | | | | | | | | | | | Create version 1.4 Signed-off-by: John Kacur <jkacur@redhat.com>
| * Add ssdd to .gitignoreJohn Kacur2019-06-191-0/+1
| | | | | | | | | | | | Add ssdd to .gitignore Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: ssdd: Add a simple manpage for ssddJohn Kacur2019-06-192-0/+30
| | | | | | | | | | | | | | Add a simple manpage to rt-tests for ssdd, and modify the manpage to install it Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: ssdd: Add Licence information to ssddJohn Kacur2019-06-191-0/+7
| | | | | | | | | | | | | | Add License Information to ssdd Signed-off-by: John Kacur <jkacur@redhat.com> Signed-off-by: Joe Korty <joe.korty@concurrent-rt.com>
| * rt-migrate-test: Add duration command line argumentDaniel Wagner2019-06-192-1/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the test programs have the --loop argument for automatic stopping. The main problem with the --loop argument is how long is --loop 1000? To simplify automated tests introduce a --duration argument which allows to set the time how long a test should run. This allows the test suite to define the execution time and also the timeout which a normal human can understand. For example run the test for 10 minutes and timeout at 11 minutes: # timeout 11m rt-migrate-test -D 10m Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * svsematest: Add duration command line argumentDaniel Wagner2019-06-192-58/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the test programs have the --loop argument for automatic stopping. The main problem with the --loop argument is how long is --loop 1000? To simplify automated tests introduce a --duration argument which allows to set the time how long a test should run. This allows the test suite to define the execution time and also the timeout which a normal human can understand. For example run the test for 10 minutes and timeout at 11 minutes: # timeout 11m svsematest -D 10m Signed-off-by: Daniel Wagner <wagi@monom.org> -Fixed some dos line endings on the man page Signed-off-by: John Kacur <jkacur@redhat.com>
| * sigwaittest: Add duration command line argumentDaniel Wagner2019-06-192-58/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the test programs have the --loop argument for automatic stopping. The main problem with the --loop argument is how long is --loop 1000? To simplify automated tests introduce a --duration argument which allows to set the time how long a test should run. This allows the test suite to define the execution time and also the timeout which a normal human can understand. For example run the test for 10 minutes and timeout at 11 minutes: # timeout 11m sigwaittest -D 10m Signed-off-by: Daniel Wagner <wagi@monom.org> -Fixed up some dos line endings in the man page changes Signed-off-by: John Kacur <jkacur@redhat.com>
| * signaltest: Add duration command line argumentDaniel Wagner2019-06-192-1/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the test programs have the --loop argument for automatic stopping. The main problem with the --loop argument is how long is --loop 1000? To simplify automated tests introduce a --duration argument which allows to set the time how long a test should run. This allows the test suite to define the execution time and also the timeout which a normal human can understand. For example run the test for 10 minutes and timeout at 11 minutes: # timeout 11m signaltest -D 10m Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * cyclicdeadline: Add duration command line argumentDaniel Wagner2019-06-191-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the test programs have the --loop argument for automatic stopping. The main problem with the --loop argument is how long is --loop 1000? To simplify automated tests introduce a --duration argument which allows to set the time how long a test should run. This allows the test suite to define the execution time and also the timeout which a normal human can understand. For example run the test for 10 minutes and timeout at 11 minutes: # timeout 11m cyclicdeadline -D 10m Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * ptsematest: Add duration command line argumentDaniel Wagner2019-06-192-55/+72
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the test programs have the --loop argument for automatic stopping. The main problem with the --loop argument is how long is --loop 1000? To simplify automated tests introduce a --duration argument which allows to set the time how long a test should run. This allows the test suite to define the execution time and also the timeout which a normal human can understand. For example run the test for 10 minutes and timeout at 11 minutes: # timeout 11m ptsematest -D 10m Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * pmqtest: Add duration command line argumentDaniel Wagner2019-06-192-2/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Many of the test programs have the --loop argument for automatic stopping. The main problem with the --loop argument is how long is --loop 1000? To simplify automated tests introduce a --duration argument which allows to set the time how long a test should run. This allows the test suite to define the execution time and also the timeout which a normal human can understand. For example run the test for 10 minutes and timeout at 11 minutes: # timeout 11m pmqtest -D 10m Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * pi_stress: Rename -t command line option to -DDaniel Wagner2019-06-192-5/+10
| | | | | | | | | | | | | | | | Streamline the duration command line argument for all rt-tests. While at it also add man page. Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * pi_stress: Allow short command line argumentsDaniel Wagner2019-06-191-2/+1
| | | | | | | | | | | | | | | | | | Add optstring to getopt_long() command line parser to support the short options as it documented in the man page and also in the usage help text. Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-utils: Move parse_time_string()Daniel Wagner2019-06-193-33/+36
| | | | | | | | | | | | | | Move parse_time_string() to rt-utils.c so we can re use it. Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * queuelat: Use clock syscall for ARM 32 bitDaniel Wagner2019-06-191-5/+26
| | | | | | | | | | | | | | | | CPUs such as Cortex-M8 don't have a rdtsc instruction. Fallback using a syscall. Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt_numa.h: Remove unused functionDaniel Wagner2019-06-191-7/+0
| | | | | | | | | | | | | | | | | | | | | | | | GCC on a BeagleBoneBlack complains: In file included from src/cyclictest/cyclictest.c:39:0: src/cyclictest/rt_numa.h:253:13: warning: ‘numa_on_and_available’ defined but not used [-Wunused-function] static void numa_on_and_available() ^~~~~~~~~~~~~~~~~~~~~ Signed-off-by: Daniel Wagner <wagi@monom.org> Signed-off-by: John Kacur <jkacur@redhat.com>
| * rt-tests: hwlatdetect.py: Code clean-upJohn Kacur2019-05-231-9/+9
| | | | | | | | | | | | | | | | - Remove obsolete from __future__ - Fix spacing around calls to print, open and brackets - Fix spacing around assignments Signed-off-by: John Kacur <jkacur@redhat.com>
| * hwlatdetect: disable/enable c-state transitions during detectionClark Williams2019-05-091-1/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Recent performance tuning problems led me to realize that just running at fifo:99 and turning off interrupts isn't enough while looking for BIOS induced latencies. Power savings logic is built into most modern cpus and so must be disabled while looking for BIOS induced (SMI/NMI) latencies. Use the /dev/cpu_dma_latency mechanism to disable c-state transitions while running the hardware latency detector. Open the file /dev/cpu_dma_latency and write a 32-bit zero to it, which will prevent c-state transitions while the file is open. Signed-off-by: Clark Williams <williams@redhat.com> Signed-off-by: John Kacur <jkacur@redhat.com>
| * queuelat: Install queuelat helper scripts from the rt-tests MakefileJohn Kacur2019-05-071-0/+2
| | | | | | | | | | | | Install queuelat helper scripts from the rt-tests Makefile Signed-off-by: John Kacur <jkacur@redhat.com>
| * queuelat: Assume queuelat and queuelat scripts are in the pathJohn Kacur2019-05-071-18/+17
| | | | | | | | | | | | | | | | | | Assume queuelat and queuelat scripts are in the path. Don't hardcode their location. Write the temporary data to /usr/tmp/outfile Signed-off-by: John Kacur <jkacur@redhat.com>
| * cyclicdeadline: Free allocated resources at exitDaniel Wagner2019-04-051-1/+5
| | | | | | | | | | Signed-off-by: Daniel Wagner <daniel.wagner@siemens.com> Signed-off-by: John Kacur <jkacur@redhat.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-04-20 05:49:04 +0000