From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: [GIT PULL v2] sched: Make sleep inside atomic detection work on !PREEMPT
Date: Thu, 23 Jun 2011 00:48:48 +0200 [thread overview]
Message-ID: <20110622224844.GA3290@somewhere> (raw)
In-Reply-To: <1307712622-11104-1-git-send-email-fweisbec@gmail.com>
On Fri, Jun 10, 2011 at 03:30:18PM +0200, Frederic Weisbecker wrote:
> Ingo,
>
> Please pull the sched/core branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> sched/core
Hi Ingo,
I have added Randy's ack on the last patch. To get it, please pull the v2 in
the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
sched/core-v2
There are no other changes.
Thanks.
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (4):
> sched: Remove pointless in_atomic() definition check
> sched: Isolate preempt counting in its own config option
> sched: Make sleeping inside spinlock detection working in !CONFIG_PREEMPT
> sched: Generalize sleep inside spinlock detection
>
>
> Documentation/DocBook/kernel-hacking.tmpl | 2 +-
> Documentation/SubmitChecklist | 2 +-
> Documentation/development-process/4.Coding | 2 +-
> Documentation/ja_JP/SubmitChecklist | 2 +-
> Documentation/zh_CN/SubmitChecklist | 2 +-
> include/linux/bit_spinlock.h | 2 +-
> include/linux/hardirq.h | 4 ++--
> include/linux/kernel.h | 2 +-
> include/linux/pagemap.h | 4 ++--
> include/linux/preempt.h | 26 +++++++++++++++++---------
> include/linux/rcupdate.h | 12 ++++++------
> include/linux/sched.h | 2 +-
> kernel/Kconfig.preempt | 3 +++
> kernel/sched.c | 6 ++----
> lib/Kconfig.debug | 9 ++++++---
> 15 files changed, 46 insertions(+), 34 deletions(-)
next prev parent reply other threads:[~2011-06-22 22:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 13:30 [GIT PULL] sched: Make sleep inside atomic detection work on !PREEMPT Frederic Weisbecker
2011-06-10 13:30 ` [PATCH 1/4] sched: Remove pointless in_atomic() definition check Frederic Weisbecker
2011-06-10 13:30 ` [PATCH 2/4] sched: Isolate preempt counting in its own config option Frederic Weisbecker
2011-06-10 13:30 ` [PATCH 3/4] sched: Make sleeping inside spinlock detection working in !CONFIG_PREEMPT Frederic Weisbecker
2011-06-10 13:30 ` [PATCH 4/4] sched: Generalize sleep inside spinlock detection Frederic Weisbecker
2011-06-10 15:37 ` Randy Dunlap
2011-06-23 4:19 ` KOSAKI Motohiro
2011-06-22 22:48 ` Frederic Weisbecker [this message]
2011-07-01 12:36 ` [GIT PULL v2] sched: Make sleep inside atomic detection work on !PREEMPT Ingo Molnar
2011-07-01 12:56 ` Frederic Weisbecker
2011-07-01 12:59 ` Ingo Molnar
2011-07-01 15:05 ` Ingo Molnar
2011-07-01 16:01 ` Frederic Weisbecker
2011-07-01 16:44 ` Frederic Weisbecker
2011-07-01 17:29 ` Ingo Molnar
2011-07-02 16:53 ` Frederic Weisbecker
2011-07-03 19:49 ` Ingo Molnar
2011-07-01 16:02 ` Frederic Weisbecker
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=20110622224844.GA3290@somewhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox