On 10/25/2012 04:04 PM, Peter Maydell wrote: > On 22 October 2012 10:23, Liu Ping Fan <pingf...@linux.vnet.ibm.com> wrote: >> v1: >> https://lists.gnu.org/archive/html/qemu-devel/2012-07/msg03312.html >> >> v2: >> http://lists.gnu.org/archive/html/qemu-devel/2012-08/msg01275.html >> >> v3: >> http://lists.nongnu.org/archive/html/qemu-devel/2012-09/msg01474.html > > Is there a clear up to date description somewhere of the design and > locking strategy here somewhere? I'd rather not have to try to > reconstitute it by reading the whole patchset...
It was described somewhere in a document by Marcelo and myself. Basically the goal is to arrive at address_space_write(): rcu_read_lock() mr = lookup() mr->ref() rcu_read_unlock() mr->dispatch() mr->unref() This is the same strategy used in many places in the kernel. -- error compiling committee.c: too many arguments to function
