mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/2] [GIT PULL] tracing: Fixes old and new
Date: Fri, 12 Dec 2014 23:21:44 -0500	[thread overview]
Message-ID: <20141213042144.599602592@goodmis.org> (raw)


Linus,

Here's two fixes:

1) Discovered by Fengguang Wu's tests. I changed the parameters to
   the function graph x86 prepare_ftrace_return() call but forgot
   to update the call from entry_32 (i386 version). This patch corrects
   that.

2) I was tracing some code and found that the sched_switch tracepoint
   was showing tasks in the INTERRUPTIBLE state as RUNNING. This was
   due to the updates to convert preempt_count into a per_cpu variable.
   The tracepoint logic was made to use the task's saved_preempt_count
   which could hold a stale "PREEMPT_ACTIVE", instead of using the
   current preempt_count() call.

Please pull the latest trace-fixes-v3.18 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-fixes-v3.18

Tag SHA1: acbe5cd526bb9de84fe73d68f8d7bfcbde8ab9f4
Head SHA1: aee4e5f3d3abb7a2239dd02f6d8fb173413fd02f


Steven Rostedt (Red Hat) (2):
      ftrace/x86: Update i386 call to prepare_ftrace_return()
      tracing/sched: Check preempt_count() for current when reading task->state

----
 arch/x86/kernel/entry_32.S   | 6 +++---
 include/trace/events/sched.h | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)

             reply	other threads:[~2014-12-13  4:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13  4:21 Steven Rostedt [this message]
2014-12-13  4:21 ` [PATCH 1/2] ftrace/x86: Update i386 call to prepare_ftrace_return() Steven Rostedt
2014-12-13  4:21 ` [PATCH 2/2] tracing/sched: Check preempt_count() for current when reading task->state 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=20141213042144.599602592@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.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®