public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH 3/3] pounder/cpufreq: Skip the test if processors are not supported by cpufreq
Date: Tue, 18 Aug 2015 16:36:46 +0800	[thread overview]
Message-ID: <1439887006-17985-3-git-send-email-liwang@redhat.com> (raw)
In-Reply-To: <1439887006-17985-2-git-send-email-liwang@redhat.com>

During the pounder21/cpufreq test, it print so many errors:

[2015-08-17 08:43:24] (17818) cpufreq.bin: FAIL with code 4.
[2015-08-17 08:43:24] (17818) cpufreq.bin: START loop #2.
[2015-08-17 08:43:25] (17812) cpufreq.bin: FAIL with code 4.
[2015-08-17 08:43:25] (17812) cpufreq.bin: START loop #2.
[2015-08-17 08:43:27] (17812) cpufreq.bin: FAIL with code 4.
...

The reason is that the case canceled some cpufreq check steps before,
now reuse them to make sure it could be skiped on a system without
cpufreq support.

Signed-off-by: Li Wang <liwang@redhat.com>
---
 tools/pounder21/test_scripts/cpufreq | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/tools/pounder21/test_scripts/cpufreq b/tools/pounder21/test_scripts/cpufreq
index ba94a76..4df70a9 100755
--- a/tools/pounder21/test_scripts/cpufreq
+++ b/tools/pounder21/test_scripts/cpufreq
@@ -21,12 +21,12 @@
 
 
 # Do any CPU support cpufreq?
-#CPUFREQ_ENABLED_CPUS=`/bin/ls -lad /sys/devices/system/cpu/cpu*/cpufreq 2> /dev/null | wc -l`
+CPUFREQ_ENABLED_CPUS=`/bin/ls -lad /sys/devices/system/cpu/cpu*/cpufreq 2> /dev/null | wc -l`
 
-#if [ "$CPUFREQ_ENABLED_CPUS" -lt 1 ]; then
-#	echo "None of your CPUs support cpufreq.  Bye."
-#	exit 255
-#fi
+if [ "$CPUFREQ_ENABLED_CPUS" -lt 1 ]; then
+	echo "None of your CPUs support cpufreq.  Bye."
+	exit 255
+fi
 
 # Turn on acpi_pstate_strict to ensure that state transitions actually happen...
 if [ -f /sys/module/acpi_cpufreq/parameters/acpi_pstate_strict ]; then
-- 
1.8.3.1


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2015-08-18  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  8:36 [LTP] [PATCH 1/3] ltp/tools: remove the scripts/numa_test.sh file Li Wang
2015-08-18  8:36 ` [LTP] [PATCH 2/3] ltp/pounder: Don't let the testing log output to /dev/tty Li Wang
2015-08-18  8:36   ` Li Wang [this message]
2015-08-20 15:58     ` [LTP] [PATCH 3/3] pounder/cpufreq: Skip the test if processors are not supported by cpufreq Cyril Hrubis
2015-08-20 15:52   ` [LTP] [PATCH 2/3] ltp/pounder: Don't let the testing log output to /dev/tty Cyril Hrubis
2015-08-20 15:44 ` [LTP] [PATCH 1/3] ltp/tools: remove the scripts/numa_test.sh file Cyril Hrubis

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=1439887006-17985-3-git-send-email-liwang@redhat.com \
    --to=liwang@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox