From: Qiao Zhao <qzhao@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: jkacur@gmail.com, williams@redhat.com, Qiao Zhao <qzhao@redhat.com>
Subject: [PATCH] ptsematest, sigwaittest, pmqtest, svsematest reprot error "Could not access /sys/kernel/debug/tracing/tracing_enabled"
Date: Thu, 25 Jul 2019 10:49:15 +0800 [thread overview]
Message-ID: <20190725024915.11497-1-qzhao@redhat.com> (raw)
For current RHEL7 and RHEL8 kernel (3.10.0 and 4.18.0), we use "tracing_on"
to control tracing disable/enable. The "tracing_enabled" is not the
current value.
For RHEL bug: https://bugzilla.redhat.com/show_bug.cgi?id=1731336
E.g: # # svsematest -a -b 20us -f -i 100 -l 100 -S
...
Could not access /sys/kernel/debug/tracing/tracing_enabled
Sanity test passed. No this error msg when patched.
Signed-off-by: Qiao Zhao <qzhao@redhat.com>
---
src/pmqtest/pmqtest.c | 2 +-
src/ptsematest/ptsematest.c | 2 +-
src/sigwaittest/sigwaittest.c | 2 +-
src/svsematest/svsematest.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/pmqtest/pmqtest.c b/src/pmqtest/pmqtest.c
index 2191710..a04fc49 100644
--- a/src/pmqtest/pmqtest.c
+++ b/src/pmqtest/pmqtest.c
@@ -204,7 +204,7 @@ void *pmqthread(void *param)
char tracing_enabled_file[MAX_PATH];
strcpy(tracing_enabled_file, get_debugfileprefix());
- strcat(tracing_enabled_file, "tracing_enabled");
+ strcat(tracing_enabled_file, "tracing_on");
int tracing_enabled =
open(tracing_enabled_file, O_WRONLY);
if (tracing_enabled >= 0) {
diff --git a/src/ptsematest/ptsematest.c b/src/ptsematest/ptsematest.c
index e8a3177..5537592 100644
--- a/src/ptsematest/ptsematest.c
+++ b/src/ptsematest/ptsematest.c
@@ -131,7 +131,7 @@ void *semathread(void *param)
char tracing_enabled_file[MAX_PATH];
strcpy(tracing_enabled_file, get_debugfileprefix());
- strcat(tracing_enabled_file, "tracing_enabled");
+ strcat(tracing_enabled_file, "tracing_on");
int tracing_enabled =
open(tracing_enabled_file, O_WRONLY);
if (tracing_enabled >= 0) {
diff --git a/src/sigwaittest/sigwaittest.c b/src/sigwaittest/sigwaittest.c
index 4579f90..59f28a5 100644
--- a/src/sigwaittest/sigwaittest.c
+++ b/src/sigwaittest/sigwaittest.c
@@ -179,7 +179,7 @@ void *semathread(void *param)
char tracing_enabled_file[MAX_PATH];
strcpy(tracing_enabled_file, get_debugfileprefix());
- strcat(tracing_enabled_file, "tracing_enabled");
+ strcat(tracing_enabled_file, "tracing_on");
int tracing_enabled =
open(tracing_enabled_file, O_WRONLY);
if (tracing_enabled >= 0) {
diff --git a/src/svsematest/svsematest.c b/src/svsematest/svsematest.c
index 01083d1..8f88078 100644
--- a/src/svsematest/svsematest.c
+++ b/src/svsematest/svsematest.c
@@ -185,7 +185,7 @@ void *semathread(void *param)
char tracing_enabled_file[MAX_PATH];
strcpy(tracing_enabled_file, get_debugfileprefix());
- strcat(tracing_enabled_file, "tracing_enabled");
+ strcat(tracing_enabled_file, "tracing_on");
int tracing_enabled =
open(tracing_enabled_file, O_WRONLY);
if (tracing_enabled >= 0) {
--
2.20.1
next reply other threads:[~2019-07-25 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 2:49 Qiao Zhao [this message]
2019-07-31 15:13 ` [PATCH] ptsematest, sigwaittest, pmqtest, svsematest reprot error "Could not access /sys/kernel/debug/tracing/tracing_enabled" 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=20190725024915.11497-1-qzhao@redhat.com \
--to=qzhao@redhat.com \
--cc=jkacur@gmail.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