[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080421145525.GB9153@linux.vnet.ibm.com>
Date: Mon, 21 Apr 2008 07:55:25 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: linux-kernel@...r.kernel.org, Josh Triplett <josh@...edesktop.org>,
linux-wireless@...r.kernel.org, linux-sparse@...r.kernel.org
Subject: Re: [RFC 0/3] Examples for the new sparse context tracking functionality
On Mon, Apr 21, 2008 at 10:25:55AM +0200, Johannes Berg wrote:
>
> > At some point in the future, we might want to distinguish between
> > the different flavors of RCU -- except that there is already common
> > code that doesn't care which flavor of RCU is in use, as long as
> > some sort of RCU is present. So make that "some point in the distant
> > future"...
>
> No big deal, just declare
>
> my_specific_rcu_get() __acquires(RCU) __acquires(specificRCU);
>
> and then annotate whatever needs the specific RCU type with
> __requires(specificRCU)
Cute!!! I didn't realize you could mark a single interface with
multiple __acquires() markings.
So if there is at least one match, sparse is happy?
Thanx, Paul
--
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