|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [patch v4 00/16] push mmio dispatch out of big lock |
Date: | Thu, 25 Oct 2012 19:07:46 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1 |
On 10/25/2012 04:04 PM, Peter Maydell wrote: > On 22 October 2012 10:23, Liu Ping Fan <address@hidden> 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
[Prev in Thread] | Current Thread | [Next in Thread] |