From: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [Patch v4 1/4] KSM test case fixes - ksm01
Date: Thu, 08 Sep 2011 15:20:32 +0530 [thread overview]
Message-ID: <4E688FE8.5020701@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 183 bytes --]
Disable ksm01 test if KSM is not configured
P.S. patch checked with 'checkpatch.pl'
Signed-off-by: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
--
Regards
R.Nageswara Sastry
[-- Attachment #2: ksm01.patch --]
[-- Type: text/plain, Size: 444 bytes --]
--- ltp.orig/testcases/kernel/mem/ksm/ksm01.c 2011-09-08 11:32:12.000000000 +0200
+++ ltp/testcases/kernel/mem/ksm/ksm01.c 2011-09-08 11:35:56.000000000 +0200
@@ -106,6 +106,8 @@ void setup(void)
if (tst_kvercmp(2, 6, 32) < 0)
tst_brkm(TCONF, NULL, "2.6.32 or greater kernel required");
+ if (access(PATH_KSM, F_OK) == -1)
+ tst_brkm(TCONF, NULL, "KSM configuration is not enabled");
tst_sig(FORK, DEF_HANDLER, NULL);
TEST_PAUSE;
[-- Attachment #3: Type: text/plain, Size: 433 bytes --]
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
reply other threads:[~2011-09-08 9:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E688FE8.5020701@linux.vnet.ibm.com \
--to=rnsastry@linux.vnet.ibm.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