All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org, Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Subject: Re: Documentation of the kvm->srcu lock
Date: Mon, 09 Sep 2013 15:51:53 +0200	[thread overview]
Message-ID: <522DD279.6000605@redhat.com> (raw)
In-Reply-To: <20130909144758.6e6c0538@thhw500>

Il 09/09/2013 14:47, Thomas Huth ha scritto:
> Am Mon, 09 Sep 2013 20:26:49 +0800
> schrieb Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>:
> 
>> On 09/09/2013 08:13 PM, Paolo Bonzini wrote:
>>> Il 09/09/2013 14:00, Thomas Huth ha scritto:
>>>>
>>>>  Hi all!
>>>>
>>>> I am quite new to KVM, and I recently had to struggle with the
>>>> kvm->srcu lock a little bit ... documentation for this lock seems
>>>> to be quite sparse, I've only found some descriptions in mailing
>>>> list archives (the description at the following URL is quite good:
>>>> http://www.mail-archive.com/kvm@vger.kernel.org/msg90003.html ).
>>>>
>>>> So I wonder whether it would be helpful for others, too, if some
>>>> information about this lock was added to the documentation file
>>>> Documentation/virtual/kvm/locking.txt for example? I'd like to
>>>> suggest the following text as a first draft (using some information
>>>> from the URL above):
>>>>
>>>>  Name:		kvm->srcu
>>>>  Type:		srcu lock
>>>>  Arch:		any
>>>>  Protects:	- kvm->memslots
>>>>  		- kvm->buses
>>>>  Comment:	The srcu read lock must be held while accessing memslots (e.g.
>>>>  		when using gfn_to_* functions) and while accessing in-kernel
>>>>  		MMIO/PIO address->device structure mapping (kvm->buses).
>>>>  		The srcu index can be stored in kvm_vcpu->srcu_idx per vcpu
>>>>  		if it is needed by multiple functions.
>>>>
>>>> What do you think? Since I am not an expert in this area, extension
>>>> and/or corrections are very welcome!
>>>
>>> Yes, this looks good.  Xiao, any suggestions?
>>
>> It's nice indeed! :)
>>
>> Reviewed-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> 
> Great :-) ... ok, can you then simply pick up the above text or shall I
> submit a real patch for that file?

Sending a patch would be appreciated.

Paolo


      reply	other threads:[~2013-09-09 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 12:00 Documentation of the kvm->srcu lock Thomas Huth
2013-09-09 12:13 ` Paolo Bonzini
2013-09-09 12:26   ` Xiao Guangrong
2013-09-09 12:47     ` Thomas Huth
2013-09-09 13:51       ` Paolo Bonzini [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=522DD279.6000605@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=thuth@linux.vnet.ibm.com \
    --cc=xiaoguangrong@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.