From: Paolo Bonzini <pbonzini@redhat.com>
To: Hillf Danton <hdanton@sina.com>
Cc: Peter Gonda <pgonda@google.com>,
Sean Christopherson <seanjc@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] KVM: SEV: Mark nested locking of vcpu->lock
Date: Sat, 30 Apr 2022 10:11:53 +0200 [thread overview]
Message-ID: <327afdf9-357f-71c7-fd45-56aa41aeb134@redhat.com> (raw)
In-Reply-To: <20220430015008.4257-1-hdanton@sina.com>
On 4/30/22 03:50, Hillf Danton wrote:
> lock for migration
> ===
> kvm_for_each_vcpu(i, vcpu, kvm) {
> if (mutex_lock_killable(&vcpu->mutex))
> goto out_unlock;
> lockdep_copy_map(&vcpu->v_dep_map, &vcpu->mutex.dep_map);
> mutex_release(&vcpu->mutex.dep_map, ip);
> }
>
>
> unlock for migration
> ===
> kvm_for_each_vcpu(i, vcpu, kvm) {
> lockdep_copy_map(&vcpu->mutex.dep_map, &vcpu->v_dep_map);
> /*
> * Or directly acquire without v_dep_map added
> *
> mutex_acquire(&vcpu->mutex.dep_map, 0, 1,_RET_IP_);
> */
> mutex_unlock(&vcpu->mutex);
> }
Yes this is exactly what Peter is doing, except that we're trying to
keep one lock taken. Thanks for pointing to lock_sock_nested().
Paolo
next prev parent reply other threads:[~2022-04-30 8:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 19:59 Peter Gonda
2022-04-07 21:17 ` John Sperbeck
2022-04-08 15:08 ` Peter Gonda
2022-04-20 20:14 ` Peter Gonda
2022-04-21 15:56 ` Paolo Bonzini
2022-04-26 19:06 ` Peter Gonda
2022-04-27 16:04 ` Paolo Bonzini
2022-04-27 20:18 ` Peter Gonda
2022-04-28 21:28 ` Peter Gonda
2022-04-28 23:59 ` Paolo Bonzini
2022-04-29 15:35 ` Peter Gonda
2022-04-29 15:38 ` Paolo Bonzini
2022-04-29 15:51 ` Peter Gonda
2022-04-29 15:58 ` Paolo Bonzini
2022-04-29 17:12 ` Peter Gonda
2022-04-29 17:21 ` Paolo Bonzini
2022-04-29 17:27 ` Peter Gonda
2022-04-29 17:32 ` Paolo Bonzini
2022-04-29 17:33 ` Peter Gonda
[not found] ` <20220429010312.4013-1-hdanton@sina.com>
2022-04-29 8:48 ` Paolo Bonzini
[not found] ` <20220429114012.4127-1-hdanton@sina.com>
2022-04-29 13:44 ` Paolo Bonzini
[not found] ` <20220430015008.4257-1-hdanton@sina.com>
2022-04-30 8:11 ` Paolo Bonzini [this message]
2022-04-30 8:11 ` Paolo Bonzini
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=327afdf9-357f-71c7-fd45-56aa41aeb134@redhat.com \
--to=pbonzini@redhat.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pgonda@google.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®