From: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [Patch v4 4/4] KSM test case fixes - oom01 and oom03
Date: Thu, 08 Sep 2011 15:23:45 +0530 [thread overview]
Message-ID: <4E6890A9.8020405@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 191 bytes --]
Disable oom01, oom03 tests 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: mem.patch --]
[-- Type: text/plain, Size: 495 bytes --]
--- ltp.orig/testcases/kernel/mem/lib/mem.c 2011-09-08 11:32:12.000000000 +0200
+++ ltp/testcases/kernel/mem/lib/mem.c 2011-09-08 11:44:30.000000000 +0200
@@ -139,6 +139,9 @@ void testoom(int mempolicy, int lite, in
tst_resm(TINFO, "start OOM testing for mlocked pages.");
oom(MLOCK, mempolicy, lite);
+ if (access(PATH_KSM, F_OK) == -1)
+ tst_brkm(TCONF, NULL, "KSM configuration is not enabled");
+
tst_resm(TINFO, "start OOM testing for KSM pages.");
oom(KSM, mempolicy, lite);
}
[-- 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:53 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=4E6890A9.8020405@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 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.