From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Zachary Amsden <zamsden@redhat.com>
Subject: Re: [PATCH 1/2] KVM: Convert kvm_lock to raw_spinlock
Date: Wed, 09 Feb 2011 11:25:17 +0200 [thread overview]
Message-ID: <4D525D7D.8080306@redhat.com> (raw)
In-Reply-To: <4D525D30.2000402@redhat.com>
On 02/09/2011 11:24 AM, Avi Kivity wrote:
> On 02/08/2011 01:55 PM, Jan Kiszka wrote:
>> Code under this lock requires non-preemptibility. Ensure this also over
>> -rt by converting it to raw spinlock.
>>
>
> Please add a code comment documenting what data under this lock
> requires it to be a raw spinlock.
>
Or better, put it in Documentation/kvm/locking.txt, which we'll try to
grow to cover all locks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-02-09 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 11:55 [PATCH 1/2] KVM: Convert kvm_lock to raw_spinlock Jan Kiszka
2011-02-09 9:24 ` Avi Kivity
2011-02-09 9:25 ` Avi Kivity [this message]
2011-02-09 12:31 ` Jan Kiszka
2011-02-09 13:20 ` Avi Kivity
2011-02-09 13:38 ` Avi Kivity
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=4D525D7D.8080306@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=zamsden@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;
as well as URLs for NNTP newsgroup(s).