From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/4] tracing: Some fixes for 5.13
Date: Fri, 18 Jun 2021 09:20:46 -0400 [thread overview]
Message-ID: <20210618132046.600413369@goodmis.org> (raw)
Tracing fixes for 5.13:
- Have recordmcount check for valid st_shndx otherwise some archs may have
invalid references for the mcount location.
- Two fixes done for mapping pids to task names. Traces were not showing
the names of tasks when they should have.
- Fix to trace_clock_global() to prevent it from going backwards
Peter Zijlstra (1):
recordmcount: Correct st_shndx handling
Steven Rostedt (VMware) (3):
tracing: Do not stop recording cmdlines when tracing is off
tracing: Do not stop recording comms if the trace file is being read
tracing: Do no increment trace_clock_global() by one
----
kernel/trace/trace.c | 11 -----------
kernel/trace/trace_clock.c | 6 +++---
scripts/recordmcount.h | 15 ++++++++++-----
3 files changed, 13 insertions(+), 19 deletions(-)
next reply other threads:[~2021-06-18 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 13:20 Steven Rostedt [this message]
2021-06-18 13:20 ` [for-linus][PATCH 1/4] recordmcount: Correct st_shndx handling Steven Rostedt
2021-06-18 13:20 ` [for-linus][PATCH 2/4] tracing: Do not stop recording cmdlines when tracing is off Steven Rostedt
2021-06-18 13:20 ` [for-linus][PATCH 3/4] tracing: Do not stop recording comms if the trace file is being read Steven Rostedt
2021-06-18 13:20 ` [for-linus][PATCH 4/4] tracing: Do no increment trace_clock_global() by one 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=20210618132046.600413369@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
all inboxes | Powered by JetHome®