It was noted that in some benchmarks (SPEC, at least), it is necessary
for a successful run to completely silence the library's output. That
includes no ERROR messages. Add an env var for the user to request this,
HUGETLB_QUIET, which if set at all will cause the library to produce no
output.
Signed-off-by: Nishanth Aravamudan <[EMAIL PROTECTED]>
---
Question: Is there any reason for __hugetlbfs_verbose to be signed?
diff --git a/debug.c b/debug.c
index 967c99c..ec536eb 100644
--- a/debug.c
+++ b/debug.c
@@ -42,6 +42,10 @@ static void __hugetlbfs_init_debug(void)
if (env)
__hugetlbfs_verbose = atoi(env);
+ env = getenv("HUGETLB_QUIET");
+ if (env)
+ __hugetlbfs_verbose = 0;
+
initialized = 1;
}
--
Nishanth Aravamudan <[EMAIL PROTECTED]>
IBM Linux Technology Center
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Libhugetlbfs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libhugetlbfs-devel
