[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131004112520.38f6f648@gandalf.local.home>
Date: Fri, 4 Oct 2013 11:25:20 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Yuanhan Liu <yuanhan.liu@...ux.intel.com>, mingo@...nel.org,
hpa@...or.com, linux-kernel@...r.kernel.org, tglx@...utronix.de,
linux-tip-commits@...r.kernel.org,
Fengguang Wu <fengguang.wu@...el.com>,
Huang Ying <ying.huang@...el.com>, lkp@...ux.intel.com
Subject: Re: [PATCH] ftrace, sched: Add TRACE_FLAG_PREEMPT_RESCHED
On Fri, 4 Oct 2013 17:16:18 +0200
Peter Zijlstra <peterz@...radead.org> wrote:
> Documentation section
>
> Ah, you missed the preemption series?
Yeah, I've seen them, just haven't looked at them too deeply yet.
>
> 1a338ac32ca6 sched, x86: Optimize the preempt_schedule() call
> c2daa3bed53a sched, x86: Provide a per-cpu preempt_count implementation
> a233f1120c37 sched: Prepare for per-cpu preempt_count
> bdb438065890 sched: Extract the basic add/sub preempt_count modifiers
> 01028747559a sched: Create more preempt_count accessors
> a787870924db sched, arch: Create asm/preempt.h
> f27dde8deef3 sched: Add NEED_RESCHED to the preempt_count
> 4a2b4b222743 sched: Introduce preempt_count accessor functions
> ea8117478918 sched, idle: Fix the idle polling state logic
> 315039862646 sched: Remove {set,clear}_need_resched
> b021fe3e2509 sched, rcu: Make RCU use resched_cpu()
> 0c44c2d0f459 x86: Use asm goto to implement better modify_and_test() functions
>
> preempt_count now includes a NEED_RESCHED and this patch shows which
> is set: N both PREEMPT_NEED_RESCHED and TIF_NEED_RESCHED, n for TIF only
> and p for preempt only.
You still need to update Documentation/trace/ftrace.txt. Search for
"need-resched" and that part will need to be updated.
Thanks,
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists