From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Add documentation for kvm->srcu lock
Date: Thu, 12 Sep 2013 18:33:42 +0200 [thread overview]
Message-ID: <5231ECE6.4000308@redhat.com> (raw)
In-Reply-To: <1378740776-1673-1-git-send-email-thuth@linux.vnet.ibm.com>
Il 09/09/2013 17:32, Thomas Huth ha scritto:
> This patch documents the kvm->srcu lock (using the information from
> a mail which has been posted by Marcelo Tosatti to the kvm mailing
> list some months ago, see the following URL for details:
> http://www.mail-archive.com/kvm@vger.kernel.org/msg90040.html )
>
> Signed-off-by: Thomas Huth <thuth@linux.vnet.ibm.com>
> Reviewed-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> ---
> Documentation/virtual/kvm/locking.txt | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/virtual/kvm/locking.txt b/Documentation/virtual/kvm/locking.txt
> index 41b7ac9..a9f366e 100644
> --- a/Documentation/virtual/kvm/locking.txt
> +++ b/Documentation/virtual/kvm/locking.txt
> @@ -151,3 +151,14 @@ Type: spinlock_t
> Arch: any
> Protects: -shadow page/shadow tlb entry
> Comment: it is a spinlock since it is used in mmu notifier.
> +
> +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.
>
Applied to kvm/queue for 3.12, thanks.
prev parent reply other threads:[~2013-09-12 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 15:32 [PATCH] KVM: Add documentation for kvm->srcu lock Thomas Huth
2013-09-12 16:33 ` 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=5231ECE6.4000308@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=thuth@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.