From: gowrishankar <gomuthuk@linux.vnet.ibm.com>
To: subrata@linux.vnet.ibm.com
Cc: ltp-list@lists.sf.net
Subject: [LTP] [PATCH] realtime: fix parameter name clash in pi-test7 due to memlock option added
Date: Tue, 07 Jul 2009 11:13:33 +0530 [thread overview]
Message-ID: <4A52E085.5070706@linux.vnet.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
Hi Subrata,
Please accept the patch below.
Apologies to resend it as I forgot to tag subject with [PATCH] previously :)
Thanks,
Gowri
---
realtime: fix parameter name clash in pi-test7 due to memlock option added
Below patch just renames the parameter name for number of mid priority threads
in pi-test7 from -m to -x. Original one clashes with our common memlock option
used across all RT tests.
Also, pi-test7 is already disabled in our default run profile, so this patch
can silently update the test without any impact on any other test.
Testing Informations:
Tested pi-test7 binary with the patch for the changes.
Signed-off-by: Gowrishankar <gowrishankar.m@in.ibm.com>
Tested-by: Gowrishankar <gowrishankar.m@in.ibm.com>
Acked-by: Sripathi Kodi <sripathik@in.ibm.com>
---
[-- Attachment #2: pi-test-7.patch --]
[-- Type: text/x-patch, Size: 1462 bytes --]
Index: ltp-full-20090630/testcases/realtime/func/pi-tests/testpi-7.c
===================================================================
--- ltp-full-20090630.orig/testcases/realtime/func/pi-tests/testpi-7.c 2009-07-03 14:34:13.000000000 +0530
+++ ltp-full-20090630/testcases/realtime/func/pi-tests/testpi-7.c 2009-07-03 14:38:14.000000000 +0530
@@ -80,7 +80,7 @@
printf("testpi-7 specific options:\n");
printf(" -i# #: number of iterations\n");
printf(" -f #: Use flag mutex\n");
- printf(" -m# #:number of mid priority threads\n");
+ printf(" -x# #:number of mid priority threads\n");
}
int parse_args(int c, char *v)
@@ -96,7 +96,7 @@
case 'i':
iterations = atoi(v);
break;
- case 'm':
+ case 'x':
med_threads = atoi(v);
break;
default:
@@ -246,11 +246,11 @@
int i,numcpus;
setup();
- rt_init("hfi:m:", parse_args, argc, argv);
+ rt_init("hfi:x:", parse_args, argc, argv);
if (!med_threads) {
printf("This test requires that at least NRCPUS medium priority threads run\n");
- printf("If it is run bound to a single CPU, you can specify -m 1\n");
+ printf("If it is run bound to a single CPU, you can specify -x 1\n");
printf("No User input , using default value for NRCPUS");
numcpus = sysconf(_SC_NPROCESSORS_ONLN);
med_threads = numcpus;
[-- Attachment #3: Type: text/plain, Size: 390 bytes --]
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
[-- 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
next reply other threads:[~2009-07-07 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 5:43 gowrishankar [this message]
2009-07-07 15:32 ` [LTP] [PATCH] realtime: fix parameter name clash in pi-test7 due to memlock option added 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=4A52E085.5070706@linux.vnet.ibm.com \
--to=gomuthuk@linux.vnet.ibm.com \
--cc=ltp-list@lists.sf.net \
--cc=subrata@linux.vnet.ibm.com \
/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