From: Kurt Kanzenbach <kurt@linutronix.de>
To: John Kacur <jkacur@redhat.com>, Clark Williams <williams@redhat.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
Kurt Kanzenbach <kurt@linutronix.de>
Subject: [PATCH 3/4] rt-tests: cyclictest: Close correct trace fds
Date: Sat, 7 Nov 2020 10:58:42 +0100 [thread overview]
Message-ID: <20201107095843.11909-4-kurt@linutronix.de> (raw)
In-Reply-To: <20201107095843.11909-1-kurt@linutronix.de>
Remove the last lefotovers from migrating cyclictest to rt-utils.
The rt-utils module is reponsible for handling the tracing code.
Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
---
src/cyclictest/cyclictest.c | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/src/cyclictest/cyclictest.c b/src/cyclictest/cyclictest.c
index 34aa9be583f8..0ec0b235dba3 100644
--- a/src/cyclictest/cyclictest.c
+++ b/src/cyclictest/cyclictest.c
@@ -283,9 +283,6 @@ enum {
ERROR_NOTFOUND = -2,
};
-static int trace_fd = -1;
-static int tracemark_fd = -1;
-
/*
* Raise the soft priority limit up to prio, if that is less than or equal
* to the hard limit
@@ -2272,10 +2269,7 @@ int main(int argc, char **argv)
}
out:
/* close any tracer file descriptors */
- if (tracemark_fd >= 0)
- close(tracemark_fd);
- if (trace_fd >= 0)
- close(trace_fd);
+ disable_trace_mark();
/* unlock everything */
if (lockall)
--
2.26.2
next prev parent reply other threads:[~2020-11-07 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 9:58 [PATCH 0/4] rt-tests: rt-utils: Close trace fds Kurt Kanzenbach
2020-11-07 9:58 ` [PATCH 1/4] rt-tests: rt-utils: Mark internal functions static Kurt Kanzenbach
2020-11-11 2:29 ` John Kacur
2020-11-07 9:58 ` [PATCH 2/4] rt-tests: rt-utils: Add function to close trace fds Kurt Kanzenbach
2020-11-11 2:30 ` John Kacur
2020-11-07 9:58 ` Kurt Kanzenbach [this message]
2020-11-11 2:32 ` [PATCH 3/4] rt-tests: cyclictest: Close correct " John Kacur
2020-11-07 9:58 ` [PATCH 4/4] rt-tests: oslat: Close " Kurt Kanzenbach
2020-11-11 2:34 ` John Kacur
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=20201107095843.11909-4-kurt@linutronix.de \
--to=kurt@linutronix.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 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.