On Thu, May 13, 2010 at 08:23:40AM -0700, Paul E. McKenney wrote:
vhost in fact does flush_work rather than
flush_workqueue, so while for now everything runs
from vhost_workqueue in theory nothing would break
if we use some other workqueue or even a combination
I guess when/if this happens, we could start by converting
to _raw and then devise a solution.
By the way what would be really nice is if we had a way
to trap when rcu protected pointer is freed without a flush
while some reader is running. Current annotation does not
allow this, does it?