Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / ltp / 755afd842e6a37e099e2d678e2b9f5e635f5a86a / testcases / realtime
  1. 0baf411 [PATCH (2/2)] splitting the tsc support. The patch moves the tsc macros form the librttest.h to another header file (named libtsc.h). Without this I got the following error and no tests were built. by subrata_modak · 15 years ago
  2. c3e4577 [PATCH (1/2)] add atomi_add() define for __sh__. Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@st.com>. by subrata_modak · 15 years ago
  3. 3a0171b Accidentally nuking your .c files when running clean isn't a good thing. by yaberauneya · 15 years ago
  4. 45e3a54 I thought I removed the recursive LDLIBS definition sneak in. Oh well... by yaberauneya · 15 years ago
  5. e4707b1 Get rid of redundant XOPEN2K #define (_GNU_SOURCE covers this). by yaberauneya · 15 years ago
  6. 5ac23b1 1. Get rid of psuedo-autoconf scripts in testcases/realtime/scripts. by yaberauneya · 15 years ago
  7. 6fb6a4f Fix a typo and a warning related to unchecked results from asprintf, punted by from the compiler. by yaberauneya · 15 years ago
  8. b3c28e7 The format string quantifier is incorrect, and thus the compiler prints out a warning. by yaberauneya · 15 years ago
  9. 01979aa Check in Makefile, which partially fixes issue with realtime component build breakage. by yaberauneya · 15 years ago
  10. 7f05328 Fix two broken Makefiles reported by Gowri at IBM. by yaberauneya · 15 years ago
  11. ce93bf4 realtime: Remove printing of cpu affinity masks in pi-tests: Some tests under realtime/func/pi-tests in LTP display junk values for cpu affinity masks: by subrata_modak · 15 years ago
  12. ef77253 1. Please see README.mk-devel for a full description of the changes by yaberauneya · 15 years ago
  13. 077a00e Patch to change the format of Steve Rostedt's rt-migrate-test testcase: This patch converts the testcase rt-migrate-test.c to the coding format used by the other realtime testcases in LTP, by making use of the librttest and libstats infrastructure. Signed-off-by: Kiran Prakash <kiran@linux.vnet.ibm.com>, Acked-by: Darren Hart <dvhltc@us.ibm.com>, Acked-by: Sripathi Kodi <sripathik@in.ibm.com>. Originally-contributed-by: Steven Rostedt <rostedt@goodmis.org>, by subrata_modak · 15 years ago
  14. 2d876b0 prio-wake: Enable using more than 95 threads: prio-wake will currently spew pthread errors on systems with more than 95 CPUS, or if an -n value > 95 is specified on the command line. To avoid this, spread threads out equally over the priorities by calculated the number of threads per priority. Tested with all pathological numbers (i.e. mod=0 mod=1, etc) of threads. Ran 10000 times in parallel. Confirmed failure continues to exist without requeue PI (as it should) and success is seen with requeue PI (as it should be). by subrata_modak · 15 years ago
  15. bf29947 prio-wake: Allow for optional locking prior to broadcast: Allow the user to decide if the mutex should be held prior to calling pthread_cond_broadcast(). Default remains the same. Tested with and without the argument as well as with both 0 and 1 passed to the argument. Values other than 0 and 1 will result in locking the mutex. by subrata_modak · 15 years ago
  16. 9533201 Use librttest arg parsing and init_pi_mutex: This patch converts pthread_cond_many to use the librttest infrastructure for argument parsing and mutex initialization. The default behavior of the test changes from using a non-pi mutex to a pi mutex. This is because -p defaults to 1 in librttest. We could update run.sh with -p0, but I feel inside a realtime testsuite this test should be using PI mutexes anyway. by subrata_modak · 15 years ago
  17. c13db75 Add support for long options: Incorporating existing tests (like pthread_cond_many) may require support for long options if the existing arguments are to remain supported. This patch adds support for long options, while keeping the default of only short options in place. long opts MUST have an equivalent short opt so as to not require changing (and complicating) the parse_arg signature. This patch tests for this in the rt_init routine. by subrata_modak · 15 years ago
  18. aacd331 This line has to be added to avoid a stupid CVS problem. Should be removed in the next commit of the same source file. by subrata_modak · 15 years ago
  19. 611fec2 [RESEND][PATCH 3/3] libstats: Modify testcases to call the append function. I am resending the patch after checking with the latest CVS version of LTP. by subrata_modak · 15 years ago
  20. 1897ec4 This set of 3 patches adds a new API stats_container_append to libstats. This function adds new stats_record_t to the record list in stats_container_t. It also replaces the occurrences of data->size with data->index and modifies the test-cases to call the append function. Changelog by subrata_modak · 15 years ago
  21. f842cac This set of 3 patches adds a new API stats_container_append to libstats. This function adds new stats_record_t to the record list in stats_container_t. It also replaces the occurrences of data->size with data->index and modifies the test-cases to call the append function. Changelog by subrata_modak · 15 years ago
  22. 9319701 This set of 3 patches adds a new API stats_container_append to libstats. This function adds new stats_record_t to the record list in stats_container_t. It also replaces the occurrences of data->size with data->index and modifies the test-cases to call the append function. Changelog by subrata_modak · 15 years ago
  23. 504d949 realtime: Fix the pass criterion of pi_perf test case: The pass criterion in pi_perf test case is wrong. It compares the minimum amount of time taken by the low priority thread with the maximum amount of time taken by the high priority thread to calculate the PI delay. Obviously, these min and max don't necessarily happen in the same iteration, resulting in a number of false failures. The correct way is to compare the time taken by low and high priority threads in each iteration and then find the maximum delay experienced by high priority thread across the iterations. This patch implements the change. Additionally, this patch removes lock_wait_dat array, which is not needed anymore as well as makes a couple of messages easier to understand. This patch changes the messages displayed by this test case slightly. They look like the following now: by subrata_modak · 15 years ago
  24. 4ed6f47 realtime: fix parameter name clash in pi-test7 due to memlock option added: Below patch just renames the parameter name for number of mid priority threads in pi-test7 from -m to -x. Original one clashes with our common memlock option used across all RT tests. Also, pi-test7 is already disabled in our default run profile, so this patch can silently update the test without any impact on any other test. Testing Informations: Tested pi-test7 binary with the patch for the changes. Signed-off-by: Gowrishankar <gowrishankar.m@in.ibm.com>. by subrata_modak · 15 years ago
  25. 27fdaaa Realtime: use mlockall optionally in realtime tests: Below patch adds the support to enable memory lock in realtime testcases optionally (with -m). Testing Informations: Tested the realtime tests in their default profile and as well as using mlock option. by subrata_modak · 15 years ago
  26. e6432e4 [real-time] sched_footbal atomic start: The current barrier implementation results in the lowest priority thread actually starting the game (they are the last to be scheduled to call pthread_barrier_wait). This thread likely gets a priority boost as it holds the hb->lock for the futex associated with the barrier. This might lead to it running ahead of the defense threads. In fact, any sort of barrier or cond var implementation (short of a pi aware cond broadcast, which is not yet readily available) will result in a thundering herd situation when the FUTEX_WAKE_ALL syscall is issued, which can result in a short run of one or more offense threads while all the threads get to the RUNNABLE state. This patch removes the complex starting mechansims and replaces them with a simple atomic counter. All player threads are started and once the players_ready count reaches the total player count, the referee starts the game by setting the ball position to zero. Tested on two platforms (both x86_64, 4 and 8-way) for a combined total of 13,000 iterations with 0 failures. Signed-off-by: Darren Hart <dvhltc@us.ibm.com>. by subrata_modak · 15 years ago
  27. 56a3116 Fix faulty interpretation of PASS/FAIL bysched_football log parser: The log parser of sched_football sometimes interprets successful runs as FAILed ones as it gets the final result based on the PASS/FAIL value of the first run in the log file. The rationale behind this patch is that sched_football testcase can itself decide if it has passed or failed based on the_ball value. There is no need of the log parser as is the case with the other test cases like pi_perf. Changelog: by subrata_modak · 16 years ago
  28. 56f4d75 Realtime: fix testpi2 parser from invalid index type error: realtime: fix testpi2 parser from invalid index type error. The patch below fixes invalid array index returned by eval() function in testpi2 parser. While a typical testpi2 logfile, where text fragment "pthread pol 2 pri 10" follows 'Noise Thread' line more than once, is given to testpi2 parser, it exits with error below: by subrata_modak · 16 years ago
  29. f20da5d Rename description files. While working on adding a new testcase I noticed that not all of the description files are named consistently. I guess that 00_ was meant to place it first in any directory listing so presumably that's the correct description name. Signed-off-by: Matt Helsley <matthltc@us.ibm.com>. by subrata_modak · 16 years ago
  30. 7e66474 Realtime: Usability fix for matrix_mult test case: Here is a simple usability fix for matrix_mult test case. I think this print statement was missed out when the test was written. by subrata_modak · 16 years ago
  31. 503be94 realtime: add time out option to gtod_infinite test: At present, gtod_infinite runs for ever, until we kill the test. This behavior blocks the automated codes to use it as part of running it and generating result graphs. Below patch adds the option to timeout the test after specified hours (-t option, which is for number of hours). With out using this option, test runs for infinite hours which is its default behavior. Also, this patch is first step on gtod_infinite to add it into future patch for long_running tests, where it may be scheduled to run for 3 days. Signed-off-by: Gowrishankar M <gowrishankar.m@in.ibm.com>. Acked-By: Dinakar Guniguntala <dino@in.ibm.com>. by subrata_modak · 16 years ago
  32. cfc246a The following patch fixes two problems in loop variables of gtod_latency test case: by subrata_modak · 16 years ago
  33. e75e9ee Remove libjvmsim: This patch removes the libjvmsim itself. Hence no testcase can use it anymore. Signed-Off-By: Chirag <chirag@linux.vnet.ibm.com>, Acked-By: Sripathi Kodi <sripathik@in.ibm.com>. by subrata_modak · 16 years ago
  34. 4ce8327 Remove references of jvmsim from the tests: Most of the testcases, have an option (-j) which runs the jvmsim as a background load so as to simulate the behavior of the JVM.This patch removes the references of jvmsim from all the testcases. Signed-Off-By: Chirag <chirag@linux.vnet.ibm.com>, Acked-by: Sripathi Kodi <sripathik@in.ibm.com>. by subrata_modak · 16 years ago
  35. 94b2d00 Fix busy loop in realtime: by subrata_modak · 16 years ago
  36. 39c8f45 The test case gtod_latency in realtime causes soft lockups on some machines. This is because the test hogs the cpus for a long time, because it's main loop runs at SCHED_FIFO, 99. We have seen soft lockups mainly on LS20 machines (x86_64, Opterons). The following patch introduces a sleep after some iterations of the test. This ensures that the test doesn't hog the cpu completely and hence avoids soft lockups. by subrata_modak · 16 years ago
  37. c7528c8 This patch adds librt debug support for prio-wake. The log level selected is 0, as it necessary to print all the buffered information. Tested: by subrata_modak · 16 years ago
  38. b716705 This patch ensures that prio-preempt uses the librt debug mechanism. Tested: Running the test: by subrata_modak · 16 years ago
  39. 78645ad matrix_mult.c: concurrent calculation stats fix: by subrata_modak · 16 years ago
  40. 2f706fb matrix_mult.c: thread synchronisation simplification: by subrata_modak · 16 years ago
  41. 88ae347 matrix_mult.c: dynamic iterations configuration. by subrata_modak · 16 years ago
  42. 5823fdc matrix_mult.c: set_affinity to work when there are offline cpus: by subrata_modak · 16 years ago
  43. 266d4ec librttest.c: enhancement and fixes for options handling. by subrata_modak · 16 years ago
  44. d7d5969 The clock source used in the gtod_infinite test should be CLOCK_MONOTONIC instead of CLOCK_REALTIME. This is to avoid plausible inconsistencies caused by NTP time adjustments. Tested: running gtod_infinite and then killing it. Signed-Off-By: Chirag <chirag@linux.vnet.ibm.com>, Acked-by: Darren Hart <dvhltc@us.ibm.com>. by subrata_modak · 16 years ago
  45. 76a6920 -t test-arguments Where test-argument can be a space separated sequence of: by subrata_modak · 16 years ago
  46. 9a84db5 This patch ensures that the python scripts support utf encoding. Prior to the patch, the python scripts would exit with this error: by subrata_modak · 16 years ago
  47. 7859695 This patch fixes a few minor issues in run.sh by subrata_modak · 16 years ago
  48. 0d8f525 This patch removes outdated (or irrelevant) parts of the existing documentation and updates its. Also incorporated are suggestions made by Darren. Signed-Off-By: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
  49. fd96e73 While the synchronization in the sched_football testcase under the realtime test suite is not erroneous, it can be enahnced and made more reliable by making use of pthread_barriers, like in other testcases. This patch adds the same. Testing done: Infinite iterations of the testcase run with this patch. by subrata_modak · 16 years ago
  50. 573e348 This is a patch from John, written a few months back. I have fixed up a few cosmetic whitespace bits, and have refreshed it so it should apply cleanly to LTP today. Will Schmidt <will_schmidt@vnet.ibm.com>. by subrata_modak · 16 years ago
  51. 3358671 In tsc_minus, changed test (tsc_begin < tsc_end) by (tsc_begin <= tsc_end) since values can be equal as read operations are sometimes very close. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Cc: Tim Chavez <tinytim@us.ibm.com>. Acked-by: Darren Hart <dvhltc@us.ibm.com>. by subrata_modak · 16 years ago
  52. 49309b9 This macro reads atomically the 64-bit TSC register. Reading the 64-bit register using two 32-bit instructions sometimes causes wrapping when a clock update appears in between. A single 64-bit read fixes this. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Cc: Tim Chavez <tinytim@us.ibm.com>. by subrata_modak · 16 years ago
  53. 75d0486 First patch regroups TSC functions and macros definition into librttest. Second patch is to have an atomic reading of the 64-bit timebase register of powerpc64. This new function is only valid if -m64 is used when compiling the whole testcase suite with a powerpc64. Thirs patch is a fix to avoid spurious tsc_minus warning. These patches been tested on a ppc64 machine either with 32 or 64 bit binaries. (-m64). by subrata_modak · 16 years ago
  54. b6438db When compiling powerpc binaries, gcc defaults to 32 bit. To do some tests I needed to have a 64 bit binary. Since I'm using realtime, I modified config.mk as below. My questions: is there any official way to turn LTP in 64bit? If not, what shall we do then? Should LTP default to 32 or native-arch bit? Shall we use something like: "if (uname -m) ..." or use a command line option? Any comment? by subrata_modak · 16 years ago
  55. a5765f2 This patch ensures that async_handler and async_handler_jk runs by default. Also the profile/default is updated to reflect the same. Signed-Off-By: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
  56. 2c82e33 It looks like the only thing that didn't apply was the function declaration. It builds (with a warning) and runs just fine. But here is a patch to fix the warning. Signed-off-by: Vernon Mauery <vernux@us.ibm.com>. by subrata_modak · 16 years ago
  57. 021ed25 I spent some time looking at the sched_latency test trying to see why it took so long to start the thread. The java version of the test takes a comparable amount of time to start the thread as it does for each period. The rt-test version was taking an order of magnitude longer. After digging through the java documentation, I found that the RealtimeThread does not actually start executing until the RealtimeThread.waitForNextPeriod() fulfills the time specified in the PeriodicParameters parameter included in its constructor. So all the tests are scheduled to run about 1 second after the threads are created. This gives the system plenty of time to create the thread (a non-realtime code path), set the scheduling parameters and then sleep until the specified run time. The start latency as measured by the test goes something like this: by subrata_modak · 16 years ago
  58. d04fedf Ankita Proposed that: by subrata_modak · 16 years ago
  59. 6f71555 Profiled tests - cleanup. I forgot some useless code in the scripts. These patches do the cleanup. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. by subrata_modak · 16 years ago
  60. 1ffddf0 Profiled Tests: by subrata_modak · 16 years ago
  61. 3bfea97 These patches will allow for the plotting of the max over time in discrete segments, rather than as a monotonically increasing value, while maintaining the original behavior by default. The existing test has an infinite window and report the new max each time it is increased. The patch maintains the default behavior and adds a -w option, allowing the user to specify a window (iteration count) for which the max of that window is reported ever w iterations. Signed-off-by: Darren Hart <dvhltc@us.ibm.com>. Acked-by: John Stultz <johnstul@us.ibm.com>. by subrata_modak · 16 years ago
  62. ba9a5b9 These patches will allow for the plotting of the max over time in discrete segments, rather than as a monotonically increasing value, while maintaining the original behavior by default. Cleanup some whitespace issues here. Signed-off-by: Darren Hart <dvhltc@us.ibm.com>. Acked-by: John Stultz <johnstul@us.ibm.com>. by subrata_modak · 16 years ago
  63. 0baface Modified sched_latency.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  64. ab3bbe6 Modified tc-2.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  65. 22a75d5 Modified hrtimer-prio.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  66. 758acd6 Modified pi_perf.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  67. 7288933 Modified async_handler.c and async_handler_jk.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  68. 38f5dcd Modified matrix_mult.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  69. 4786315 Modified pthread_kill_latency.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  70. ffc7b35 Modified prio-preempt.c to consider pass criteria (-c) arg. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  71. dcb0d30 Added -c arg into rt_init of librttest.c so all tests can use it. This arg sets the global variable (double) pass_criteria. librttest.h declares pass_criteria as external. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  72. cc6b329 Modified periodic_cpu_load_single.c. Changed arg -c to -l (calculation per loop). In next patch, -c arg is to be used as pass/fail criteria globally for all tests. Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com> by subrata_modak · 17 years ago
  73. 87191dd Added missing break in parse args switch/case. (-s arg). Signed-off-by: Gilles Carry <gilles.carry@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com> by subrata_modak · 17 years ago
  74. 6e619ee I believe we had written this test to debug the other test with a lower overhead clocksource. Unfortunately, the tsc is x86 specific, isn't consistent across CPUs on certain systems, and can have it's frequency changed depending on by power states. For all those reasons this test can simply be removed from the LTP. Raied by Daniel Gollub <dgollub@suse.de>, endorsed by Sebastien Dugue <sebastien.dugue@bull.net>, seconded by Darren Hart <dvhltc@us.ibm.com>. by subrata_modak · 17 years ago
  75. 7540004 Remove the last 2 files missed in the migration, namely: by subrata_modak · 17 years ago
  76. ec649c6 Some tests have a configurable number of iterations. However those same tests which do calculate quantiles need a number of iterations higher than 100. Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  77. cd9aeee periodic_cpu_load has a '-i iterations' command line argument without it being listed in the help. Add its description to the usage() function. Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  78. b1f31b1 The rttest, stats and jvmsim library archives used by the realtime tests only contain a single object file each. Therefore we can skip the "ar" and "ranlib" steps and directly link with the objects. Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com>. by subrata_modak · 17 years ago
  79. 71189c6 pi_perf is not built by default, so add it to SUBDIRS in testcases/realtime/Makefile. Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net>. Acked-by: Chirag <chirag@linux.vnet.ibm.com> by subrata_modak · 17 years ago
  80. d0f013f Now that the realtime tests are part of the LTP, there is no need to have any longer specific compilation directives comments in the source files. And in most cases they are incorrect. Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net>. Cc: Darren Hart <dvhltc@us.ibm.com> by subrata_modak · 17 years ago
  81. d79e1a1 checks return values of asprintf calls else gcc-4.3.0 fails like following; by subrata_modak · 17 years ago
  82. 4a174f9 dont stick ar flags into AR, and dont set AR/RANLIB by default by vapier · 17 years ago
  83. ab889c6 split CFLAGS/CPPFLAGS properly and remove inappropriate flags by vapier · 17 years ago
  84. fb02e2a Fixes a minor issue with pi_perf testcase (testcases/realtime/func/). The wait_dat is intended to measure the amount of time it took for the high priority thread to actually obtain the lock from the time it was released by the low priority thread. The patch fixes this computation to measure it more accurately. The PASS/FAIL computation is unaffected. Signed-off-by: Ankita Garg <ankita@in.ibm.com>, Acked-by: Sripathi Kodi <sripathik@in.ibm.com> by subrata_modak · 17 years ago
  85. 26b2c9a This patch updates the matrix_mult testcase to closely follow the JVM in the concurrent case. So in the concurrent case we have 'numcpus-1' concurrent threads that are handed out work by the main thread and once we run out of concurrent threads, the main thread does the work itself. Signed-off-by: Dinakar Guniguntala <dino@in.ibm.com> by subrata_modak · 17 years ago
  86. 30b7df2 Usually the cross compiler is set from the toplevel directory by setting the CROSS_COMPILER variable. This makefile tries to overwrite it, but wrong. It is also possible to push in CFLAGS from the toplevel by using CROSS_CFLAGS. We should use these here as well. Finally, LDFLAGS are set here but not used by the makefiles. Moving the posix libs to LDLIBS makes it build. Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de> by subrata_modak · 17 years ago
  87. 6856fb1 Fix by Michael Olbrich <m.olbrich@pengutronix.de>, as, Sebastien´s Patch [[PATCH 3/3] [Realtime] Remove autotools specific stuff] applied on 24/03/2008 breaks this script. by subrata_modak · 17 years ago
  88. bfd58c8 Forgot to remove include/rttests_config.h.in in the previous patch. Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net> by subrata_modak · 17 years ago
  89. 58f0b1a Remove autotools stuff: by subrata_modak · 17 years ago
  90. d104a94 Add Makefiles to all the realtime testcases without any autotools dependencies. Signed-off-by: Sebastien Dugue <sebastien.dugue@bull.net> by subrata_modak · 17 years ago
  91. 51a6d8b Add 2 scripts for detecting features used by some tests, namely: by subrata_modak · 17 years ago
  92. ac423fd Whitespaces cleanup and added -i argument for iterations, by, Gilles Carry <gilles.carry@bull.net> by subrata_modak · 17 years ago
  93. 1db2f5c We have seen that prio_preempt testcase that is part of realtime tests occasionally hangs. This can be easily recreated on a 8-cpu system, but can be recreated on a 4-cpu system as well when run for a number of iterations. The problem occurs because the first worker thread sometimes fails to call cond_wait on the condvar through which the master thread signals it to start. Since the first thread needs to start the chain of signalling from then on, all other threads just sit in a cond_wait without ever being woken up. The fix is to have a barrier to ensure that the first worker thread doesn't miss the cond_signal. I have tested this patch by running 10s of thousands of iterations of the testcase. Without the patch I can recreate the problem fairly easily, by, Sripathi Kodi <sripathik@in.ibm.com> by subrata_modak · 17 years ago
  94. 8349b3f In a lot of cases, we do not really care about the samples and histogram files and their associated gnuplot command files or do not want to save them for example on embedded platforms with limited or no storage. This patch disables generating those files by default and introduce a new parameter to the tests, namely '-s', for when we really want to. by subrata_modak · 17 years ago
  95. 255d032 1. Whitespaces cleanup by subrata_modak · 17 years ago
  96. 4cfd91c This file uses pthread_mutex_lock(), which needs posix.h. by subrata_modak · 17 years ago
  97. 2ddd737 1. Minor fixes: by subrata_modak · 17 years ago
  98. 188f280 This patch fixes the testcases mismerge due to the patch "There are numerous cleanups, fixes and features went into our ..." from Sudhanshu Singh. Turned out there was less damage than I thought. Hopefully, it should restore the fixes and cleanups which were reverted before the February Release. by subrata_modak · 17 years ago
  99. d93eb3e 1) The pi-tests don't use the librttest infrastructure and simply duplicate code. This patch ensures that those tests use librttest. by subrata_modak · 17 years ago
  100. 1378205 There are numerous cleanups, fixes and features went into our locally maintained version of realtime tests, since its intergration in LTP december last year. This patch merges those changes into LTP tree. The patch majorly contains : by subrata_modak · 17 years ago