At the moment we don't have reliable way to enumerate
all possible values, which can be used. They are dependent
on both kernel version and kernel config.
Based on previous discussion here:
http://article.gmane.org/gmane.linux.ltp/14146/match=sched_relax_domain_level
it seems better to get rid of this testcase, rather than testing
internal knobs, which can change at anytime.
Signed-off-by: Jan Stancek <[email protected]>
---
.../cpuset_base_ops_testset.sh | 27
+-------------------
1 files changed, 1 insertions(+), 26 deletions(-)
diff --git a/testcases/kernel/controllers/cpuset/cpuset_base_ops_test/cpuset_base_ops_testset.sh b/testcases/kernel/controllers/cpuset/cpuset_base_ops_test/cpuset_base_ops_testset.sh
index 2b1016e..1b84996 100755
--- a/testcases/kernel/controllers/cpuset/cpuset_base_ops_test/cpuset_base_ops_testset.sh
+++ b/testcases/kernel/controllers/cpuset/cpuset_base_ops_test/cpuset_base_ops_testset.sh
@@ -176,28 +176,6 @@ test_flags()
done # for filename in flagfiles
}
-test_domain()
-{
- cfile_name="sched_relax_domain_level"
- while read domain_level result
- do
- base_op_test "$CPUSET/sched_relax_domain_level" "$domain_level" "$result"
- done <<- EOF
- NULL 0
- 0 0
- 1 1
- 2 2
- 3 3
- 4 4
- 5 5
- 6 WRITE_ERROR
- -1 -1
- -2 WRITE_ERROR
- A WRITE_ERROR
- EOF
- # while read domain_level result
-}
-
# attach_task_test <cpus> <mems> <expect>
attach_task_test()
{
@@ -288,10 +266,7 @@ test_mems
# Case 36-83
test_flags
-# Case 84-94
-test_domain
-
-# Case 95-97
+# Case 84-86
test_attach_task
exit $exit_status
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
