From: Daniel Wagner <dwagner@suse.de>
To: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org, Daniel Wagner <dwagner@suse.de>
Subject: [PATCH rt-tests v1 06/13] pip_stress: Move test result output to main
Date: Thu, 4 Mar 2021 20:22:13 +0100 [thread overview]
Message-ID: <20210304192220.11272-7-dwagner@suse.de> (raw)
In-Reply-To: <20210304192220.11272-1-dwagner@suse.de>
Instead printing the result high() close directly move it to main()
function to simplify the return code if the test fails.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
src/pi_tests/pip_stress.c | 15 +++++++--------
1 file changed, 7 insertions(+), 8 deletions(-)
diff --git a/src/pi_tests/pip_stress.c b/src/pi_tests/pip_stress.c
index 8b91578f9ab8..2c3288984202 100644
--- a/src/pi_tests/pip_stress.c
+++ b/src/pi_tests/pip_stress.c
@@ -146,6 +146,7 @@ int main(int argc, char *argv[])
exit(1);
} else if (pid1 != 0) { /* parent code */
low(pid1);
+ exit(0);
} else { /* child code */
pid2 = fork(); /* parent code */
if (pid2 == -1) {
@@ -155,9 +156,15 @@ int main(int argc, char *argv[])
high(pid2);
} else { /* child code */
medium();
+ exit(0);
}
}
+ if (statep->inversion)
+ printf("Successfully used priority inheritance to handle an inversion\n");
+ else
+ printf("No inversion incurred\n");
+
exit(0);
}
@@ -222,14 +229,6 @@ void high(pid_t pid)
Pthread_mutex_unlock(resource);
kill(pid, SIGKILL); /* kill the medium thread */
waitpid(pid, &status, 0);
-
- Pthread_mutex_lock(statep->mutex);
-
- if (statep->inversion)
- printf("Successfully used priority inheritance to handle an inversion\n");
- else
- printf("No inversion incurred\n");
- Pthread_mutex_unlock(statep->mutex);
}
/* mmap a page of anonymous shared memory */
--
2.30.1
next prev parent reply other threads:[~2021-03-04 19:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 19:22 [PATCH rt-tests v1 00/13] JSON cleanups and more tests updated Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 01/13] cyclictest: Fix printf format specifier Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 02/13] cyclicdeadline.c: " Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 03/13] signaltest: Add missing --output usage info Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 04/13] rt_util: Copy command line before getopt_long() is called Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 05/13] rt-util: Add start time of test execution for JSON output Daniel Wagner
2021-03-04 19:22 ` Daniel Wagner [this message]
2021-03-04 19:22 ` [PATCH rt-tests v1 07/13] pip_stress: Return failure code if test fails Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 08/13] pip_stress: Prepare arg parser to accept only long options Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 09/13] pip_stress: Add JSON output feature Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 10/13] pi_stress: Prepare command line parser for long options only Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 11/13] pi_stress: Add JSON output feature Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 12/13] ssdd: Add quiet command line option Daniel Wagner
2021-03-04 19:22 ` [PATCH rt-tests v1 13/13] ssdd: Add JSON output feature Daniel Wagner
2021-03-05 7:04 ` Daniel Wagner
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=20210304192220.11272-7-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).