From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] KVM: Start lock documentation
Date: Sun, 06 Mar 2011 11:40:00 +0200
Message-ID: <4D735670.9050204@redhat.com>
References: <4D52A090.5010308@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:5218 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751553Ab1CFJkH (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 6 Mar 2011 04:40:07 -0500
In-Reply-To: <4D52A090.5010308@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 02/09/2011 04:11 PM, Jan Kiszka wrote:
> The goal of this document shall be
> - overview of all locks used in KVM core
> - provide details on the scope of each lock
> - explain the lock type, specifically of a raw spin locks
> - provide a lock ordering guide
>
> Start with one dependency chain and two locks.
>

Applied, with the dependency chain omitted, thanks.

Future patches which affect locking will be required to update this 
document.

-- 
error compiling committee.c: too many arguments to function