From: "Radim Krčmář" <rkrcmar@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Jirka Hladký" <jhladky@redhat.com>,
"Jiří Vozár" <jvozar@redhat.com>,
x86@kernel.org
Subject: [PATCH 0/2] sched/debug: add sched_update_nr_running tracepoint
Date: Tue, 3 Sep 2019 17:43:38 +0200 [thread overview]
Message-ID: <20190903154340.860299-1-rkrcmar@redhat.com> (raw)
Add a tracepoint for monitoring nr_running values, which is helpful in
discovering scheduling imbalances.
More information and most of the code is in [2/2], while [1/2] fixes a
build issue that popped up because CREATE_TRACE_POINTS is now defined
for several includes.
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Jirka Hladký <jhladky@redhat.com>
Cc: Jiří Vozár <jvozar@redhat.com>
Cc: x86@kernel.org
Radim Krčmář (2):
x86/mm/tlb: include tracepoints from tlb.c instead of mmu_context.h
sched/debug: add sched_update_nr_running tracepoint
arch/x86/include/asm/mmu_context.h | 2 --
arch/x86/mm/tlb.c | 2 ++
include/trace/events/sched.h | 22 ++++++++++++++++++++++
kernel/sched/core.c | 7 ++-----
kernel/sched/fair.c | 2 --
kernel/sched/sched.h | 7 +++++++
6 files changed, 33 insertions(+), 9 deletions(-)
--
2.23.0
next reply other threads:[~2019-09-03 15:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 15:43 Radim Krčmář [this message]
2019-09-03 15:43 ` [PATCH 1/2] x86/mm/tlb: include tracepoints from tlb.c instead of mmu_context.h Radim Krčmář
2019-09-03 15:43 ` [PATCH 2/2] sched/debug: add sched_update_nr_running tracepoint Radim Krčmář
2019-09-03 16:05 ` Valentin Schneider
2019-09-04 4:23 ` Joel Fernandes
2019-09-04 8:14 ` Peter Zijlstra
2019-09-04 10:52 ` Qais Yousef
2019-09-04 13:11 ` Joel Fernandes
2019-09-04 15:26 ` Alexei Starovoitov
2019-09-04 15:33 ` Joel Fernandes
2019-09-04 15:37 ` Alexei Starovoitov
2019-09-04 15:41 ` Joel Fernandes
2019-09-04 10:43 ` Qais Yousef
2019-09-04 13:06 ` Joel Fernandes
2019-09-04 14:20 ` Qais Yousef
2019-09-04 14:41 ` Joel Fernandes
2019-09-04 14:57 ` Qais Yousef
2019-09-04 15:46 ` Joel Fernandes
2019-09-04 15:25 ` Alexei Starovoitov
2019-09-04 15:40 ` Joel Fernandes
2019-09-04 15:51 ` Alexei Starovoitov
2019-09-04 17:47 ` Peter Zijlstra
2019-09-04 17:53 ` Alexei Starovoitov
2019-09-05 8:13 ` Ingo Molnar
2019-09-05 16:49 ` Alexei Starovoitov
2019-09-04 6:55 ` chengjian (D)
2019-09-04 13:13 ` Peter Zijlstra
2019-09-04 13:21 ` Valentin Schneider
2019-09-04 14:37 ` Qais Yousef
2019-09-04 17:48 ` Peter Zijlstra
2019-09-09 10:59 ` Qais Yousef
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=20190903154340.860299-1-rkrcmar@redhat.com \
--to=rkrcmar@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jhladky@redhat.com \
--cc=jvozar@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).