From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Mel Gorman <mgorman@techsingularity.net>,
Matt Fleming <matt@codeblueprint.co.uk>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Subject: [PATCH 0/2] sched/debug: more schedstats fixes
Date: Tue, 7 Jun 2016 14:43:15 -0500 [thread overview]
Message-ID: <cover.1465322027.git.jpoimboe@redhat.com> (raw)
Fixes for two more bugs I found in the schedstats code, in addition to
to the other patches I sent out:
https://lkml.kernel.org/r/cover.1464994423.git.jpoimboe@redhat.com
Josh Poimboeuf (2):
sched/debug: fix 'schedstats=enable' cmdline option
sched/debug: fix deadlock when enabling sched events
include/trace/events/sched.h | 30 +++++++++++++++---------------
kernel/sched/core.c | 26 +++++++++++++++++++++-----
kernel/sched/fair.c | 29 +++++++----------------------
3 files changed, 43 insertions(+), 42 deletions(-)
--
2.4.11
next reply other threads:[~2016-06-07 19:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 19:43 Josh Poimboeuf [this message]
2016-06-07 19:43 ` [PATCH 1/2] sched/debug: fix 'schedstats=enable' cmdline option Josh Poimboeuf
2016-06-08 8:06 ` Mel Gorman
2016-06-08 14:21 ` [tip:sched/core] sched/debug: Fix " tip-bot for Josh Poimboeuf
2016-06-07 19:43 ` [PATCH 2/2] sched/debug: fix deadlock when enabling sched events Josh Poimboeuf
2016-06-07 19:54 ` Peter Zijlstra
2016-06-07 21:02 ` Josh Poimboeuf
2016-06-08 8:13 ` Mel Gorman
2016-06-07 21:06 ` Josh Poimboeuf
2016-06-08 7:56 ` Ingo Molnar
2016-06-08 13:12 ` Josh Poimboeuf
2016-06-08 13:15 ` Ingo Molnar
2016-06-13 7:32 ` [PATCH v2] " Josh Poimboeuf
2016-06-14 11:35 ` [tip:sched/urgent] sched/debug: Fix " tip-bot for Josh Poimboeuf
2016-06-08 8:11 ` [PATCH 2/2] sched/debug: fix " Mel Gorman
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=cover.1465322027.git.jpoimboe@redhat.com \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.