From: Poornima Nayak <mpnayak@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net, arun@linux.vnet.ibm.com,
svaidy@linux.vnet.ibm.com, ego@in.ibm.com
Subject: [LTP] [Patch 2/8] Power management master script modified to integrate ILB testcase
Date: Fri, 28 Aug 2009 15:44:49 +0530 [thread overview]
Message-ID: <20090828101449.12177.9632.sendpatchset@localhost.localdomain> (raw)
In-Reply-To: <20090828101440.12177.32012.sendpatchset@localhost.localdomain>
Power management master script modified to integrate ILB testcases
Signed-off-by: poornima nayak <mpnayak@linux.vnet.ibm.com>
diff -uprN ltp_orig/testcases/kernel/power_management/runpwtests.sh ltp/testcases/kernel/power_management/runpwtests.sh
--- ltp_orig/testcases/kernel/power_management/runpwtests.sh 2009-08-28 10:54:59.000000000 +0530
+++ ltp/testcases/kernel/power_management/runpwtests.sh 2009-08-28 12:29:52.000000000 +0530
@@ -69,7 +69,7 @@ is_dual_core; dual_core=$?
#Checking sched_mc sysfs interface
#check_config.sh config_sched_mc || RC=$?
TST_COUNT=1
-if [ $multi_socket -eq $YES -a $dual_core -eq $YES ] ; then
+if [ $multi_socket -eq $YES -a $multi_core -eq $YES ] ; then
if [ -f /sys/devices/system/cpu/sched_mc_power_savings ] ; then
if test_sched_mc.sh ; then
tst_resm TPASS "SCHED_MC sysfs tests"
@@ -232,7 +232,7 @@ if [ $# -gt 0 -a "$1" = "-exclusive" ];
if [ $hyper_threaded -eq $YES ]; then
for sched_smt in `seq 0 $max_sched_smt`; do
for work_load in ${work_loads_list}; do
- : $(( TST_COUNT += 1 ))
+ : $(( TST_COUNT += 1 ))
sched_mc_smt_pass_cnt=0
for repeat_test in `seq 1 10`; do
# Testcase to validate CPU consolidation for
@@ -260,6 +260,60 @@ if [ $# -gt 0 -a "$1" = "-exclusive" ];
done
analyze_core_consolidation_result $sched_smt $work_load $sched_smt_pass_cnt
fi
+ # Verify ILB runs in same package as workload
+ if [ $multi_socket -eq $YES -a $multi_core -eq $YES ]; then
+ work_loads_list="ebizzy kernbench"
+ for sched_mc in `seq 0 $max_sched_mc`; do
+ for work_load in ${work_loads_list}
+ do
+ : $(( TST_COUNT += 1 ))
+ ilb_test.py -c $sched_mc -w $work_load; RC=$?
+ if [ $RC -eq 0 ]; then
+ tst_resm TPASS "ILB & workload in same package for sched_mc=$sched_mc"
+ else
+ if [ $sched_mc -eq 0 ]; then
+ tst_resm TPASS "ILB & workload is not in same package when sched_mc=0"
+ else
+ tst_resm TFAIL "ILB did not run in same package"
+ fi
+ fi
+ done
+ if [ $hyper_threaded -eq $YES ]; then
+ for sched_smt in `seq 0 $max_sched_smt`; do
+ for work_load in ${work_loads_list}; do
+ : $(( TST_COUNT += 1 ))
+ ilb_test.py -c $sched_mc -t sched_smt -w $work_load; RC=$?
+ if [ $RC -eq 0 ]; then
+ tst_resm TPASS "ILB & workload in same package for sched_mc=$sched_mc"
+ else
+ if [ $sched_mc -eq 0 ]; then
+ tst_resm TPASS "ILB & workload is not in same package when sched_mc=0"
+ else
+ tst_resm TFAIL "ILB did not run in same package"
+ fi
+ fi
+ done
+ done
+ fi
+ done
+ fi
+ if [ $multi_socket -eq $YES -a $hyper_threaded -eq $YES -a $multi_core -eq $YES ]; then
+ for sched_smt in `seq 0 $max_sched_smt`; do
+ for work_load in ${work_loads_list}; do
+ : $(( TST_COUNT += 1 ))
+ ilb_test.py -t $sched_smt -w $work_load; RC=$?
+ if [ $RC -eq 0 ]; then
+ tst_resm TPASS "ILB & workload not load not in same package for sched_smt=$sched_smt"
+ else
+ if [ $sched_smt -eq 0 ]; then
+ tst_resm TPASS "Its oky if ILB is not in same package when sched_smt=0"
+ else
+ tst_resm TFAIL "ILB did not run in same package"
+ fi
+ fi
+ done
+ done
+ fi
fi
exit $RC
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-28 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 10:14 [LTP] [Patch 1/8] New testcase to validate Ideal Load Balancer Functionality Poornima Nayak
2009-08-28 10:14 ` Poornima Nayak [this message]
2009-08-30 17:36 ` [LTP] [Patch 2/8] Power management master script modified to integrate ILB testcase Subrata Modak
2009-08-28 10:14 ` [LTP] [Patch 3/8] Patch to integrate ILB testcase to LTP Poornima Nayak
2009-08-30 17:36 ` Subrata Modak
2009-08-28 10:15 ` [LTP] [Patch 4/8] Addional new reusable functions for ILB testing Poornima Nayak
2009-08-30 17:36 ` Subrata Modak
2009-08-28 10:15 ` [LTP] [Patch 5/8] Modified library functions based on review comments Poornima Nayak
2009-08-30 17:36 ` Subrata Modak
2009-08-28 10:15 ` [LTP] [Patch 6/8] Included new function to check feature versus kernel version Poornima Nayak
2009-08-30 17:36 ` Subrata Modak
2009-08-28 10:15 ` [LTP] [Patch 7/8] Patch for cpu_consolidation to incorporate changes in reusable function Poornima Nayak
2009-08-30 17:36 ` Subrata Modak
2009-08-28 10:15 ` [LTP] [Patch 8/8]Patch to modify Readme file as new functionality testcase is integrated Poornima Nayak
2009-08-30 17:37 ` Subrata Modak
2009-08-30 17:36 ` [LTP] [Patch 1/8] New testcase to validate Ideal Load Balancer Functionality Subrata Modak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090828101449.12177.9632.sendpatchset@localhost.localdomain \
--to=mpnayak@linux.vnet.ibm.com \
--cc=arun@linux.vnet.ibm.com \
--cc=ego@in.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=svaidy@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.