From: liubo <liubo2009@cn.fujitsu.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] mem/hugetlb: fix failure of hugemmap04
Date: Fri, 13 Nov 2009 17:23:05 +0800 [thread overview]
Message-ID: <4AFD2579.6060107@cn.fujitsu.com> (raw)
Testcase hugemmap04 needs at least one hugepage to test,
so there needs a judgement of "number of hugepages".
This patch fixed the problems.
Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
---
testcases/kernel/mem/hugetlb/hugemmap/hugemmap04.c | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap04.c b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap04.c
index 050a071..e67e43c 100644
--- a/testcases/kernel/mem/hugetlb/hugemmap/hugemmap04.c
+++ b/testcases/kernel/mem/hugetlb/hugemmap/hugemmap04.c
@@ -72,6 +72,7 @@
#include "test.h"
#include "usctest.h"
+#include "system_specific_hugepages_info.h"
#define BUFFER_SIZE 256
@@ -124,6 +125,11 @@ main(int ac, char **av)
tst_exit();
}
+ /* Check number of hugepages */
+ if (get_no_of_hugepages() <= 0 || hugepages_size() <= 0)
+ tst_brkm(TBROK, cleanup, "Test cannot be continued owning to \
+ sufficient availability of Hugepages on the system");
+
/* Perform global setup for test */
setup();
--
1.6.2.2
------------------------------------------------------------------------------
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 reply other threads:[~2009-11-13 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 9:23 liubo [this message]
2009-11-16 8:13 ` [LTP] [PATCH] mem/hugetlb: fix failure of hugemmap04 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=4AFD2579.6060107@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.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.