- 78bdcd1 Update to OpenHPI 2.12.0 (see www.openhpi.org for more info) by subrata_modak · 16 years ago
- 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
- 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
- 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
- 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
- d742a43 It replaces nested arithmetic operations following example from Open Group specifications, in order to avoid issues with different shells, like dash from Ubuntu Gutsy. Signed-off-by: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- 83d727e I get compile error in hackbench. With the following patch, the compiler error is gone. Signed-off-by: Masatake YAMATO <yamato@redhat.com>. by subrata_modak · 16 years ago
- e32e669 I found some typos. I cannot remember but maybe I introduced. Signed-off-by: Masatake YAMATO<yamato@redhat.com>. by subrata_modak · 16 years ago
- 18dc0c2 Sorry, I took mistake in giving value to TST_* in io_setup01.c and io_submit01.c. Signed-off-by: Masatake YAMATO <yamato@redhat.com>. by subrata_modak · 16 years ago
- 317251d The following problem i found: by subrata_modak · 16 years ago
- 1026f0c The attached patch fixes the following issue: The selinux-testsuite file sigiotask testcase (run as test_fileop_t) needs rw permission to terminals to proceed its execution, which is not allowed by the non refpolicies provided in the testsuite. Ramon de Carvalho Valle <rcvalle@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- 1b90e1a Add the block device I/O bandwidth controller (io-throttle) testcase. See testcase documentation for design and implementation details. See also: http://lkml.org/lkml/2008/7/4/143. Signed-off-by: Andrea Righi <righi.andrea@gmail.com>. by subrata_modak · 16 years ago
- f9e551b Error occured, when i tried to compile ltp on ia64 box. There is a patch to fix it. similar patch on i386/x86_64 has been applied. (http://marc.info/?l=ltp-list&m=121257587007213&w=2). Signed-off-by: Shi Weihua <shiwh@cn.fujitsu.com>. by subrata_modak · 16 years ago
- 967caaf According to the manpages io_submit() can return the value: EAGAIN Insufficient resources are available to queue any iocbs. We should handle this opportunely trying to re-submit the AIO request again. Maybe an even better approach could be to just sleep a bit before trying to re-submit the request. In any case this would resolve a never-ending loop in aio01.c, where io_getevents() can be continuously called without having issued any actual request if io_submit() failed with -EAGAIN. Signed-off-by: Andrea Righi <righi.andrea@gmail.com>. by subrata_modak · 16 years ago
- c5792c9 Porting of io_destroy(), io_getevents(), io_setup() & io_submit() syscall tests from Crackerjack to LTP, by Masatake YAMATO <yamato@redhat.com>. by subrata_modak · 16 years ago
- 4a4e689 It eliminates the potential for many false negatives. by subrata_modak · 16 years ago
- 3593a50 This patch uses strcpy() instead of strcat(). strcat() should only be used when the 'dest' argument is NULL terminated. In this case, path_buffer is not initialised and so may not contain a NULL character. strcpy() will do the right thing and copy the string to the beginning of path_buffer. Matt Fleming <mjf@gentoo.org>. by subrata_modak · 16 years ago
- e753fd7 There were some mistakes in my previous patch. by subrata_modak · 16 years ago
- 1522cca I've attached some patches that I created for LTP at work. Most of them simply add command-line options to specify the amount of memory/pages to use for tests. However, there's one fix that works around a bug in uClibc's pthread implementation. Check for SYS_getuid32 and SYS_getgid32, these are the versions provided by some architectures. Matt Fleming <mjf@gentoo.org>. by subrata_modak · 16 years ago
- f413e9a I've attached some patches that I created for LTP at work. Most of them simply add command-line options to specify the amount of memory/pages to use for tests. However, there's one fix that works around a bug in uClibc's pthread implementation.Allow the number of iterations to be specified on the command line. Matt Fleming <mjf@gentoo.org>. by subrata_modak · 16 years ago
- 27efa4c I've attached some patches that I created for LTP at work. Most of them simply add command-line options to specify the amount of memory/pages to use for tests. However, there's one fix that works around a bug in uClibc's pthread implementation.Don't place an upper limit on the amount of time a nanosleep(2) call should take. The nanosleep(2) call will suspend execution for _at least_ the specified time, no upper limit is guaranteed. Matt Fleming <mjf@gentoo.org>. by subrata_modak · 16 years ago
- b6ecbe3 I've attached some patches that I created for LTP at work. Most of them simply add command-line options to specify the amount of memory/pages to use for tests. However, there's one fix that works around a bug in uClibc's pthread implementation. Allow the number of pages to use for the test to be specified on the command-line. Fix a memory leak. Also, call _exit(2) from child processes which avoids the child calling the atexit functions that the pthread library setup. This fixes an issue where the pthread manager thread would begin exiting at the same time as a child thread. The child thread would run the atexit functions which cause it to wait for a signal to be sent from the thread manager. As the thread manager was trying to exit that signal would never be sent. Calling _exit(2) from the child avoids this whole mess.Matt Fleming <mjf@gentoo.org>. by subrata_modak · 16 years ago
- 7e61536 I've attached some patches that I created for LTP at work. Most of them simply add command-line options to specify the amount of memory/pages to use for tests. However, there's one fix that works around a bug in uClibc's pthread implementation. It can be unsafe to call exit(3) from a signal handler. Call _exit(2) instead. by subrata_modak · 16 years ago
- be923e8 I've attached some patches that I created for LTP at work. Most of them simply add command-line options to specify the amount of memory/pages to use for tests. However, there's one fix that works around a bug in uClibc's pthread implementation. Allow the amount of memory to be used to be passed as a command-line argument. Matt Fleming <mjf@gentoo.org>. by subrata_modak · 16 years ago
- d040d03 Fixes the following issues: by subrata_modak · 16 years ago
- d371282 TEST_RETURN should not be inverted when logging. Signed-off-by: Masatake YAMATO <yamato@redhat.com>. by subrata_modak · 16 years ago
- 666a2ec Fix a bug in the selinux testsuite makefile, pointed out by David Howells. Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>. by subrata_modak · 16 years ago
- c5e3223 Every once in a while, pselect01 fails with the following output: by subrata_modak · 16 years ago
- f91d8ad I've tried LTP and found some wrong mode at creating file/dir in LTP source files. Here is a patch. Junjiro Okajima<hooanon05@yahoo.co.jp>. by subrata_modak · 16 years ago
- 8e1b00f Changes to fix Build, Install and run on non-supported architectures. by subrata_modak · 16 years ago
- 23ddcbc Few Changes to ttype value. by subrata_modak · 16 years ago
- 5121ac4 I forget everytime to give execute permissions to the Shell scripts. Odd way of providing permission :-) by subrata_modak · 16 years ago
- e17b51c hackbench tests the Linux scheduler. Initial test was written by Rusty Russell <rusty@rustcorp.com.au>. Later modified by Pierre Peiffer <pierre.peiffer@bull.net>, Ingo Molnar <mingo@elte.hu>, Arjan van de Ven <arjan@infradead.org>, "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>, Nathan Lynch <ntl@pobox.com> and others. Included in LTP by Subrata Modak<subrata@linux.vnet.ibm.com>, after Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>. by subrata_modak · 16 years ago
- feb4541 I'd like to use the mechanism you introduced in io_* testcases. So I've made 'io_cancel' string in the script and Makefile a variable to avoid mistake. I made the patch from testcases/kernel/syscalls/io_cancel/Makefile, not from ltp/testcases/kernel/syscalls/io_cancel/Makefile. Is this acceptable. CVS reports like testcases/kernel/syscalls/io_cancel/Makefile. Signed-off-by: Masatake YAMATO <yamato@redhat.com>. by subrata_modak · 16 years ago
- 06e466f This was ported from the Crackerjack Project by Masatake YAMATO <yamato@redhat.com>. by subrata_modak · 16 years ago
- 939b23a Here it is. Based on my last patch. by subrata_modak · 16 years ago
- bb20e79 Will be adding connectors in Future here. by subrata_modak · 16 years ago
- 49dcfa0 Addition of Initial set of Process Event Connectors by Li Zefan. Process event connector is a netlink connector that reports process events to userspace, and currently we have 5 kinds of process events, i.e. fork, exit, exec, uid, gid. There are total 5 test cases to test its functionality. But the test is not run by default, because I don't find a way to decide whether the underlying kernel supports this feather or not. Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>. by subrata_modak · 16 years ago
- 5a69089 Attached a new patch just to add the same fixes I provided you for icpm and tcp network stress as well. On SH4 STB with STLinux distribution we are able to run all the network stress tests without any failures. Due to configuration issues we do not run the multi-diffnic tests (because they require plural Network cards for host). It modifies the command sent to the remote host to kill tcp/icmp clients. It also deletes the address before setting it to avoid the following error: "RTNETLINK answers: File exists". This implies that the test fails. Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@st.com>. by subrata_modak · 16 years ago
- 7bbff8c This modifies the command sent to the remote host just to kill the ns-udpclient script. Indeed, it seems that the previous string always returns 1. Moreover, it adds a new check to verify if the return value is not empty. It could happen, for example, if the RSH returns sometime the following error: poll: protocol failure in circuit setup. Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@st.com>. by subrata_modak · 16 years ago
- 36b8a4d Running the UDP network stress tests on my SH4 target I have had to modify the following scripts: killall_udp_traffic and udp4-multi-diffip01. It deletes the address before setting it to avoid the following error: RTNETLINK answers: File exists; it implies that the test fails. Signed-off-by: Giuseppe Cavallaro <peppe.cavallaro@st.com>. by subrata_modak · 16 years ago
- 2e4cc0b Fixed the way how to run the "tc" command on the remote machine. Otherwise, we always get the following message on the local side: The remote host does not have netem functionality. Signed-off-by: Giuseppe Cavallaro@st.com. by subrata_modak · 16 years ago
- 482deaf Addition of enhanced test plan by Cai Qian <qcai@redhat.com>. by subrata_modak · 16 years ago
- 47471f7 This patch fix a concurrency issue in semctl06. The IPC keys used for this test could conflict with keys from another task. Signed-off-by: Matthieu Fertré <mfertre@irisa.fr>. by subrata_modak · 16 years ago
- 0e1f085 I found wrong format string usage in ltp/testcases/kernel/syscalls/exit/exit02.c: returned value from strerror is not used. Signed-off-by: Masatake YAMATO <yamato@redhat.com>. by subrata_modak · 16 years ago
- cd6dc3f I've ported a testcase for gettid() from crackerjack to ltp. I've added a directory ltp/testcases/kernel/syscalls/gettid. Signed-off-by: Masatake YAMATO <yamato@redhat.com> by subrata_modak · 16 years ago
- 37fabcf signal_test_05 failed on ia64 and x86_64, the following message outputed: by subrata_modak · 16 years ago
- 0d165eb signal_test_01 failed on ia64, the following message outputed: by subrata_modak · 16 years ago
- f6e1b03 Looks like the else is missing since in both the cases where flag is set to one or not we get the test broken print. Signed-off-by: Max Stirling <vickyirobot@gmail.com>. by subrata_modak · 16 years ago
- 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
- 95d95b4 Included the statement: by subrata_modak · 16 years ago
- abecc21 Fix a bug in the sigiotask test and enable the test_fdreceive policy to build against the latest refpolicy headers. Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>. by subrata_modak · 16 years ago
- dd5adf0 Force the catch_sighup to be volatile in order to overcome an issue due to the compiler optimization. In fact, compiling the test with -Os the catch_sighup variable is not set to 1 into the signal handler. At runtime, the test remain in a loop. No problem compiling without Os or O2. by subrata_modak · 16 years ago
- c310e56 Reverting back the changes done to fcntl-lock tests in May 2008 release, as this would have canceled the operation Revision *1.1 *done on the /Mon Sep 11 20:40:52 2006 UTC/ by /mreed10 /which added "A patch that added new functionality into the NFSvf lock tests. by subrata_modak · 16 years ago
- 0417704 mallocstress stresses the VMM and C library by spawning N threads which malloc blocks of increasing size until malloc returns NULL. It occur because test doesn't wait for all thread started. already started threads begin allocate memory, so pthread_create can return ENOMEM. my patch added this synchronizing. I use semaphore, because it can wait-for-zero unlike pthread_mutex. sorry, forgot set permission in semget, new patch attached. Andrew Vagin <avagin@gmail.com>. by subrata_modak · 16 years ago
- c064135 This patch fixes the writetest.c to return proper status on Failure/Success. At present the return code of the writest.c is 'zero' for both Success and Failure. As per norms non-zero value should be returned for error , so fixing this testcase. Signed off : Veerendra C <vechandr@in.ibm.com>. by subrata_modak · 16 years ago
- 44bbe6b I execute fork12 test and OMM killer begin send SIGKILL to its children and fork return success always. fork12 hang up in this case, so I create the patch (see attach), which check whether someone child killed and if it occur, return number of forked processes. Andrew Vagin <avagin@gmail.com>. by subrata_modak · 16 years ago
- 0528188 On ia64, __clone2() is used instead of clone(). Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>. by subrata_modak · 16 years ago
- 2743968 utimensat() syscall was introduced from linux-2.6.22 onwards. Michael wrote the initial testcases, and, the same is being contributed to LTP under GPLv2. I worked out a patch for this. Though this is not using LTP specific libraries at the moment. But the tests run well and tests 99 separate variations. Michael has written it through itś length and breadth. I generated the code coverage (9.2%) over 2.6.25-gcov kernel, which however was not built with <make allmodconfig> option. Please see it attached along with a draft man page of utimensat(), created by Michael. Let us know how do you feel about this test. We can then go ahead and add this to LTP. Signed-off-by Michael Kerrisk <mtk.manpages@googlemail.com>. Signed-off-by: Subrata Modak <subrata@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- 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
- a649d52 Currently, timerfd01 test case blocks building process for architectures that haven’t prepared for it. This patch modify it to be more generic for all architectures. Roy Lee <roylee@andestech.com>. by subrata_modak · 16 years ago
- b230c64 Add syscall numbers for timerfd syscalls under i386 and x86_64. Roy Lee <roylee@andestech.com>. by subrata_modak · 16 years ago
- 75164c3 This patch fix the make file of fs_bin test case so that it can be cross-built. Roy Lee <roylee@andestech.com>. by subrata_modak · 16 years ago
- e909dfc time-schedule01 failed, because it sent SIGTERM to itself before program exited, so the return value is not 0. This patch makes the main process ignore SIGTERM. Li Zefan <lizf@cn.fujitsu.com>. by subrata_modak · 16 years ago
- 39fe977 After the patch from Roy moveing the libtestsuite code from /testcases/kernel/syscalls/lib to /lib, the code in the old directory has not been removed. Moreover, include PATH in some makefile was still pointing to this old directory. This patch remove libtestsuite code from the old directory and remove deprecated references to this old dir in some Makefiles. Renaud Lottiaux <Renaud.Lottiaux@kerlabs.com>. by subrata_modak · 16 years ago
- a4b89a8 The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. cleanup() is reserved for the main test process. In children, call exit() instead. Signed-off-by: Louis Rilling <Louis.Rilling@kerlabs.com>. by subrata_modak · 16 years ago
- 7432850 The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. In a child, calling waitpid() to wait for the death of sibling child is simply non-sense. Moreover in execve05, the second child does not need such synchronization. Remove it. Signed-off-by: Louis Rilling <Louis.Rilling@kerlabs.com>. by subrata_modak · 16 years ago
- dfe328c The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. In execve05, the first child must keep a file open at least until the second child tries to execve() this file. However the test achieves this with a sleep of 10s, which may fail on loaded systems. This patch replaces this (arbitrary) sleep with a pipe-based synchronization, where the parent notifies the first child once the second child has terminated. Signed-off-by: Louis Rilling <Louis.Rilling@kerlabs.com>. by subrata_modak · 16 years ago
- ed56540 The following patches fix execve05 for error reporting when execve() succeeds, and exit synchronization in loaded systems. The last two patches are minor cleanups. execve05 checks that execve() fails if a process has opened the file with write access. However, in case the test fails and execve() succeeds, the default binary (test3) has return code 0, which is interpreted as test success. We get output like that: by subrata_modak · 16 years ago
- 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
- 4464067 This patch fix a concurrency issue in mremap04. The tmp directory the IPC key was build with was destroyed before we destroy the IPC ressource attached to the key. In case of concurency, the same inode id can be reused for another process tmp dir, leading to the generation of the same key. Renaud Lottiaux <Renaud.Lottiaux@kerlabs.com>. by subrata_modak · 16 years ago
- 50512d9 CPU and MEMORY HOTPLUG test cases picked up from http://devresources.linux-foundation.org/dev/hotplug/. by subrata_modak · 16 years ago
- af2c9ef These tests were contributed by the timerfd() syscall developer Davide Libenzi <davidel@xmailserver.org>. by subrata_modak · 16 years ago
- 3deda4b This patch addresses the review comments for recently accepted memory controller testcases (failcnt test and stat_check test). Signed-off-by: Sudhir Kumar <skumar@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- d04fedf Ankita Proposed that: by subrata_modak · 16 years ago
- af16e52 According to man sigpause : by subrata_modak · 16 years ago
- 091b5e0 This patch adds the documentation for memory controller. Signed-off-by: Sudhir Kumar <skumar@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- 9e65c8b This patch adds the stat check test case for memory controller. In this test a task runs in a group with some memory limit and does some memory allocation. The script checks the memory usage field from two files under the controller, the memory.usage_in_bytes and memory.stat. It reports pass if the two values are same and fail if the two values differ. Signed-off-by: Sudhir Kumar <skumar@linux.vnet.ibm.com>. Acked-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- 5c7971b This patch adds the failcnt check test for memory controller. In this test a task runs in a group with some memory limit and does total memory allocation greater than the limit of the group. The script checks the failcnt from memory.failcnt file under the controller. It reports pass if failcnt increases otherwise reports fail. Signed-off-by: Sudhir Kumar <skumar@linux.vnet.ibm.com>. Acked-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- 2f4de1d This patch fixes the output of the test, so all fatal errors to cause the final failure of the test will be printed out as FAIL instead of INFO, and all verbose and debug output will be moved to STDERR instead of STDOUT for easy output processing. Signed-off-by: Cai Qian <qcai@redhat.com>. by subrata_modak · 16 years ago
- 8a9ecb7 This patch adds a list for all known issues which are probably subtle to be fixed in kernel to the test, so the test could continue. Also, it will print out those expected failures as INFO or WARN to the test result. Signed-off-by: Cai Qian <qcai@redhat.com>. by subrata_modak · 16 years ago
- 1d1d22b Restored back the Makefile content. Else, there will be build/clean/install failures. Subrata Modak <subrata@linux.vnet.ibm.com>. by subrata_modak · 16 years ago
- 8f2ef4a Manas K Nayak <maknayak@in.ibm.com> updated the fnctl lock tests from http://nfsv4.bullopensource.org/tools/tests/locktest.php. I have retained some info like the deploy_info, etc from the older release as well. The old tests were failing. After updates, the test passes. by subrata_modak · 16 years ago
- 69bc3dc I got the following failure: by subrata_modak · 16 years ago
- 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
- e272235 execve02 checks that execve() fails if the caller does not have executable permission on the file. However, in case the test fails and execve() succeeds, the default binary (test3) has return code 0, which is interpreted as test success. We get output like that: by subrata_modak · 16 years ago
- 7a2fd9b I got failures on ptrace03 because the latest kernel allows init process to be traced. The commit is: by subrata_modak · 16 years ago
- cced845 This patch fix a concurrency issue in msgctl06. The tmp directory the IPC key was build with was destroyed before we destroy the IPC ressource attached to the key. In case of concurency, the same inode id can be reused for another process tmp dir, leading to the generation of the same key. Regards Renaud Lottiaux <Renaud.Lottiaux@kerlabs.com>. by subrata_modak · 16 years ago
- 1ffddf0 Profiled Tests: by subrata_modak · 16 years ago
- 0de2c12 The earlier patch broke parisc (which has really some strange requirements). Attached patch fixes it. If it's OK for you, please apply. By, Helge Deller <deller@gmx.de>. by subrata_modak · 16 years ago
- 9a0748e Put-libtestsuite-to-a-more-common-place.patch by subrata_modak · 16 years ago
- 8791f67 Make-sync_pipe-API-more-generic-and-update-related.patch. by subrata_modak · 16 years ago
- 5c7ad45 Both of the above test cases has similar issue to shmt/mmap series. This patch removes the non-aligned addresses explicitly coded for different architectures by: by subrata_modak · 16 years ago
- ee2924a Roy Lee <roylee17@gmail.com> wrote: by subrata_modak · 16 years ago
- 3b8e06c I see Roy's patch was already checked in. In principle I agree with the patch, but a few things are wrong now and IMHO does not fulfill what it should test any longer. shm05.c -> see my (untested!!!) patch below. Some architectures can only map at specific offsets. Current version "sucessfully" fails, because e.g. hppa can't map at cp+4096. So, it's not failing because the memory regions overlap, although that was intended to be tested...shm06.c now does basically the same test as shm04.c ?!? Doesn't make sense... I would revert the patch for shm06, but maybe others think different???? Other patches seem ok, although I haven't looked too deep into them yet... Helge Deller <deller@gmx.de>. by subrata_modak · 16 years ago
- 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
- 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
- 78b1912 This patch modifies testcases to attach their shm segment to addresses chosen by ststem instead of arch-dependent ones. I looked into the history of these testcases, but couldn't find the reason why they specified arch-dependent addresses in the first place. If it has something to do with the page coloring issue, SHMLBA should be in some manners instead of defining arch-dependent addresses. Tested successfully on ia64, ppc64, x86_64, s390x & i386 by Subrata Modak <subrata@linux.vnet.ibm.com>, and by Martin Habets <errandir_news@mph.eclipse.co.uk> on sparc32. Signed-off-by: Roy Lee <roylee17@gmail.com>. by subrata_modak · 16 years ago
- f665c2b The fixed address passed to mmap() should be aligned to the value of SHMLBA as defined in sys/shm.h (The same fix can be found in the mmap01 case earlier sent from Martin Habets ). By, Roy Lee <roylee17@gmail.com>. by subrata_modak · 16 years ago
- 1d1937a This patch adds a few tests for a variety of bind mounts. More than just shared subtrees are involved as plain --bind and plain --move are used. Read-only bind mounts are not covered by these tests however. Avantika Mathur originally wrote the tests. I've ported them to use LTP APIs and conventions. I've also modified Avantika's scripts to try and robustly cleanup after broken tests so that leftover mounts and failures at any point in a test are cleaned up thoroughly. I've made what efforts I can to follow the conventions I found in LTP FAQs and the source however there's alot here so I may have missed something. Shared bind mounts were introduced in 2.6.15. Because of this we need a tst_kvercmp command which can be invoked from a script. I've added this to ltpapicmd.c. This patch applies to the April release of LTP. I'll also be posting results for x86, x86_64, and ppc64 on a variety of kernels. In order to highlight the results contributed by this patch I've only run this portion of the patched LTP. Comments welcome. Signed-off-by: Matt Helsley <matthltc@us.ibm.com>. by subrata_modak · 17 years ago