From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:47395)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1bkDoS-0001n3-EQ
	for qemu-devel@nongnu.org; Wed, 14 Sep 2016 13:17:33 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1bkDoN-0006tG-8w
	for qemu-devel@nongnu.org; Wed, 14 Sep 2016 13:17:32 -0400
Received: from mail-yw0-f196.google.com ([209.85.161.196]:35096)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rth7680@gmail.com>) id 1bkDoN-0006sq-3l
	for qemu-devel@nongnu.org; Wed, 14 Sep 2016 13:17:27 -0400
Received: by mail-yw0-f196.google.com with SMTP id u82so1486281ywc.2
	for <qemu-devel@nongnu.org>; Wed, 14 Sep 2016 10:17:27 -0700 (PDT)
Sender: Richard Henderson <rth7680@gmail.com>
References: <1473678761-8885-1-git-send-email-pbonzini@redhat.com>
From: Richard Henderson <rth@twiddle.net>
Message-ID: <e77e9c72-a5b6-0d70-425b-51980312d074@twiddle.net>
Date: Wed, 14 Sep 2016 10:16:23 -0700
MIME-Version: 1.0
In-Reply-To: <1473678761-8885-1-git-send-email-pbonzini@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v7 00/16] cpu-exec: Safe work in quiescent
 state
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, sergey.fedorov@linaro.org

On 09/12/2016 04:12 AM, Paolo Bonzini wrote:
> In addition to fixing some of the issues found by Alex, safe work items
> need not run anymore with a mutex taken.  Of course, cpu_exec_start/end
> and start_exclusive/end_exclusive are essentially the read and write
> side of a specialized rwlock, so there is still a lock in disguise looming
> to cause deadlocks; however, it does removes worries about recursive
> locking from CPU list manipulations.
> 
> The new patches are 8, 12 and 13.  Patch 12 of v6 has been split
> across patch 10 and patch 16.
> 
> Paolo
> 
> v6->v7: Do not separate qemu_work_item and SafeWorkItem
>         More cleanups/optimizations of exclusive section logic

What tree is this based on?
The patch set doesn't apply cleanly to master or v2.7.0.


r~