From: Sean Christopherson <seanjc@google.com>
To: Hao Peng <flyingpenghao@gmail.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: use unified srcu interface function
Date: Fri, 9 Dec 2022 01:22:06 +0000 [thread overview]
Message-ID: <Y5KNvgzakT1Vvxy4@google.com> (raw)
In-Reply-To: <CAPm50aJTh7optC=gBXfj+1HKVu+9U0165mYH0sjj3Jqgf8Aivg@mail.gmail.com>
On Thu, Dec 08, 2022, Hao Peng wrote:
> From: Peng Hao <flyingpeng@tencent.com>
>
> kvm->irq_routing is protected by kvm->irq_srcu.
>
> Signed-off-by: Peng Hao <flyingpeng@tencent.com>
> ---
> virt/kvm/irqchip.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/virt/kvm/irqchip.c b/virt/kvm/irqchip.c
> index 1e567d1f6d3d..90f54f04e37c 100644
> --- a/virt/kvm/irqchip.c
> +++ b/virt/kvm/irqchip.c
> @@ -216,7 +216,8 @@ int kvm_set_irq_routing(struct kvm *kvm,
> }
>
> mutex_lock(&kvm->irq_lock);
> - old = rcu_dereference_protected(kvm->irq_routing, 1);
> + old = srcu_dereference_check(kvm->irq_routing, &kvm->irq_srcu,
> + lockdep_is_held(&kvm->irq_lock));
Readers of irq_routing are protected via kvm->irq_srcu, but this writer is never
called with kvm->irq_srcu held. I do like the of replacing '1' with
lockdep_is_held(&kvm->irq_lock) to document the protection, so what about just
doing that? I.e.
diff --git a/virt/kvm/irqchip.c b/virt/kvm/irqchip.c
index 1e567d1f6d3d..77a18b4dc103 100644
--- a/virt/kvm/irqchip.c
+++ b/virt/kvm/irqchip.c
@@ -216,7 +216,8 @@ int kvm_set_irq_routing(struct kvm *kvm,
}
mutex_lock(&kvm->irq_lock);
- old = rcu_dereference_protected(kvm->irq_routing, 1);
+ old = rcu_dereference_protected(kvm->irq_routing,
+ lockdep_is_held(&kvm->irq_lock));
rcu_assign_pointer(kvm->irq_routing, new);
kvm_irq_routing_update(kvm);
kvm_arch_irq_routing_update(kvm);
> rcu_assign_pointer(kvm->irq_routing, new);
> kvm_irq_routing_update(kvm);
> kvm_arch_irq_routing_update(kvm);
> --
> 2.27.0
next prev parent reply other threads:[~2022-12-09 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 1:19 [PATCH] KVM: use unified srcu interface function Hao Peng
2022-12-09 1:22 ` Sean Christopherson [this message]
2022-12-20 7:47 ` Hao Peng
2022-12-23 15:32 ` Paolo Bonzini
2023-01-04 1:19 ` Sean Christopherson
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=Y5KNvgzakT1Vvxy4@google.com \
--to=seanjc@google.com \
--cc=flyingpenghao@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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 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.