From 652f0859bb54d04c04dc8240e07b9b97d791c180 Mon Sep 17 00:00:00 2001 From: "Paul E. McKenney" Date: Fri, 3 Feb 2006 03:04:38 -0800 Subject: [PATCH] --- yaml --- r: 19669 b: refs/heads/master c: bb3b9cf122eb097ed9fe8ae50e1b0dbba9bbe447 h: refs/heads/master i: 19667: 1d148cf02228213cd63d51e0f1c7ec0dcb4d9eb5 v: v3 --- [refs] | 2 +- trunk/include/linux/rcupdate.h | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 908affa0adec..57ed15980189 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 9d9c0531c91755a90b646b27bb722d59ee3eb46d +refs/heads/master: bb3b9cf122eb097ed9fe8ae50e1b0dbba9bbe447 diff --git a/trunk/include/linux/rcupdate.h b/trunk/include/linux/rcupdate.h index 981f9aa43353..b87aefa082e2 100644 --- a/trunk/include/linux/rcupdate.h +++ b/trunk/include/linux/rcupdate.h @@ -240,11 +240,14 @@ extern int rcu_pending(int cpu); * This means that all preempt_disable code sequences, including NMI and * hardware-interrupt handlers, in progress on entry will have completed * before this primitive returns. However, this does not guarantee that - * softirq handlers will have completed, since in some kernels + * softirq handlers will have completed, since in some kernels, these + * handlers can run in process context, and can block. * * This primitive provides the guarantees made by the (deprecated) * synchronize_kernel() API. In contrast, synchronize_rcu() only * guarantees that rcu_read_lock() sections will have completed. + * In "classic RCU", these two guarantees happen to be one and + * the same, but can differ in realtime RCU implementations. */ #define synchronize_sched() synchronize_rcu()