From: Tingwei Zhang <tingwei@codeaurora.org>
To: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@redhat.com>
Cc: Tingwei Zhang <tingwei@codeaurora.org>,
tsoni@codeaurora.org,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Mao Jinlong <jinlmao@codeaurora.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 4/4] stm class: ftrace: use different channel accroding to CPU
Date: Mon, 20 Jul 2020 10:21:17 +0800 [thread overview]
Message-ID: <20200720022117.9375-5-tingwei@codeaurora.org> (raw)
In-Reply-To: <20200720022117.9375-1-tingwei@codeaurora.org>
To avoid mixup of packets from differnt ftrace packets simultaneously,
use different channel for packets from different CPU.
Signed-off-by: Tingwei Zhang <tingwei@codeaurora.org>
---
drivers/hwtracing/stm/ftrace.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/hwtracing/stm/ftrace.c b/drivers/hwtracing/stm/ftrace.c
index ce868e095410..6c3bce11c8d3 100644
--- a/drivers/hwtracing/stm/ftrace.c
+++ b/drivers/hwtracing/stm/ftrace.c
@@ -10,7 +10,7 @@
#include <linux/stm.h>
#include <linux/trace.h>
-#define STM_FTRACE_NR_CHANNELS 1
+#define STM_FTRACE_NR_CHANNELS NR_CPUS
#define STM_FTRACE_CHAN 0
static int stm_ftrace_link(struct stm_source_data *data);
@@ -37,8 +37,9 @@ static void notrace
stm_ftrace_write(struct trace_export *export, const void *buf, unsigned int len)
{
struct stm_ftrace *stm = container_of(export, struct stm_ftrace, ftrace);
+ unsigned int cpu = smp_processor_id();
- stm_source_write(&stm->data, STM_FTRACE_CHAN, buf, len);
+ stm_source_write(&stm->data, STM_FTRACE_CHAN + cpu, buf, len);
}
static int stm_ftrace_link(struct stm_source_data *data)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-07-20 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 2:21 [PATCH 0/4] tracing: export event trace and trace_marker Tingwei Zhang
2020-07-20 2:21 ` [PATCH 1/4] stm class: ftrace: change dependency to TRACING Tingwei Zhang
2020-07-20 2:21 ` [PATCH 2/4] tracing: add trace_export support for event trace Tingwei Zhang
2020-07-21 16:37 ` Steven Rostedt
2020-07-21 16:43 ` Steven Rostedt
2020-07-21 23:54 ` tingwei
2020-07-21 23:36 ` tingwei
2020-07-20 2:21 ` [PATCH 3/4] tracing: add trace_export support for trace_marker Tingwei Zhang
2020-07-20 2:21 ` Tingwei Zhang [this message]
2020-07-21 17:55 ` [PATCH 4/4] stm class: ftrace: use different channel accroding to CPU Steven Rostedt
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=20200720022117.9375-5-tingwei@codeaurora.org \
--to=tingwei@codeaurora.org \
--cc=jinlmao@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=tsoni@codeaurora.org \
/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).