From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [patch 0/4] Markers updates for 2.6.25-rc6
Date: Wed, 19 Mar 2008 20:27:37 -0400 [thread overview]
Message-ID: <20080320002737.918213455@polymtl.ca> (raw)
Hi Andrew,
Here are a few updates for the kernel markers. One is particularity important :
the combined use of preempt_disable/enable() and call_rcu/rcu_barrier does not
mix well with PREEMPT_RCU. I added a depends !PREEMPT_RCU to the markers to this
configuration is not reached.
The proper fix will imply to implement call_sched and sched_barrier, but I don't
think it will appear before 2.6.25.
It applies on top of 2.6.25-rc6 on top of the make-marker_debug-static.patch
already in your tree in th following order :
markers-depends-on-not-preempt-rcu.patch
markers-add-comments.patch
markers-remove-access-once.patch
markers-support-for-proprietary-modules.patch
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2008-03-20 0:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 0:27 Mathieu Desnoyers [this message]
2008-03-20 0:27 ` [patch 1/4] Markers - depends on not PREEMPT_RCU Mathieu Desnoyers
2008-03-20 19:03 ` Ingo Molnar
2008-03-20 19:49 ` Paul E. McKenney
2008-03-20 0:27 ` [patch 2/4] Markers - Update preempt_disable. call_rcu, rcu_barrier comments Mathieu Desnoyers
2008-03-20 0:27 ` [patch 3/4] Markers - Remove ACCESS_ONCE Mathieu Desnoyers
2008-03-20 0:27 ` [patch 4/4] Markers Support for Proprierary Modules Mathieu Desnoyers
2008-03-20 5:35 ` Rusty Russell
2008-03-20 12:30 ` Mathieu Desnoyers
2008-03-20 8:38 ` Christoph Hellwig
2008-03-20 19:12 ` Ingo Molnar
2008-03-20 19:18 ` Jon Masters
2008-03-20 22:15 ` Ingo Molnar
2008-03-20 20:17 ` Frank Ch. Eigler
2008-03-20 22:05 ` Ingo Molnar
2008-03-20 22:24 ` Mathieu Desnoyers
2008-03-20 22:22 ` Mathieu Desnoyers
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=20080320002737.918213455@polymtl.ca \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.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