From: Andrii Nakryiko <andrii@kernel.org>
To: linux-trace-kernel@vger.kernel.org, rostedt@goodmis.org,
mhiramat@kernel.org
Cc: peterz@infradead.org, oleg@redhat.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, jolsa@kernel.org,
Andrii Nakryiko <andrii@kernel.org>
Subject: [PATCH] uprobes: get rid of bogus trace_uprobe hit counter
Date: Mon, 5 Aug 2024 13:28:03 -0700 [thread overview]
Message-ID: <20240805202803.1813090-1-andrii@kernel.org> (raw)
trace_uprobe->nhit counter is not incremented atomically, so its value
is bogus in practice. On the other hand, it's actually a pretty big
uprobe scalability problem due to heavy cache line bouncing between CPUs
triggering the same uprobe.
Drop it and emit obviously unrealistic value in its stead in
uporbe_profiler seq file.
The alternative would be allocating per-CPU counter, but I'm not sure
it's justified.
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
---
kernel/trace/trace_uprobe.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/kernel/trace/trace_uprobe.c b/kernel/trace/trace_uprobe.c
index 52e76a73fa7c..5d38207db479 100644
--- a/kernel/trace/trace_uprobe.c
+++ b/kernel/trace/trace_uprobe.c
@@ -62,7 +62,6 @@ struct trace_uprobe {
struct uprobe *uprobe;
unsigned long offset;
unsigned long ref_ctr_offset;
- unsigned long nhit;
struct trace_probe tp;
};
@@ -821,7 +820,7 @@ static int probes_profile_seq_show(struct seq_file *m, void *v)
tu = to_trace_uprobe(ev);
seq_printf(m, " %s %-44s %15lu\n", tu->filename,
- trace_probe_name(&tu->tp), tu->nhit);
+ trace_probe_name(&tu->tp), ULONG_MAX);
return 0;
}
@@ -1507,7 +1506,6 @@ static int uprobe_dispatcher(struct uprobe_consumer *con, struct pt_regs *regs)
int ret = 0;
tu = container_of(con, struct trace_uprobe, consumer);
- tu->nhit++;
udd.tu = tu;
udd.bp_addr = instruction_pointer(regs);
--
2.43.5
next reply other threads:[~2024-08-05 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 20:28 Andrii Nakryiko [this message]
2024-08-06 7:37 ` [PATCH] uprobes: get rid of bogus trace_uprobe hit counter Jiri Olsa
2024-08-06 17:26 ` Andrii Nakryiko
2024-08-07 21:43 ` Masami Hiramatsu
2024-08-09 18:43 ` Andrii Nakryiko
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=20240805202803.1813090-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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