From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Start lock documentation
Date: Sun, 06 Mar 2011 11:40:00 +0200 [thread overview]
Message-ID: <4D735670.9050204@redhat.com> (raw)
In-Reply-To: <4D52A090.5010308@siemens.com>
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
prev parent reply other threads:[~2011-03-06 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 14:11 [PATCH] KVM: Start lock documentation Jan Kiszka
2011-02-09 14:18 ` Jan Kiszka
2011-02-15 16:44 ` Marcelo Tosatti
2011-02-15 17:07 ` Avi Kivity
2011-02-15 17:08 ` Jan Kiszka
2011-02-16 9:03 ` Avi Kivity
2011-03-06 9:40 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D735670.9050204@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox