From: Alex Williamson <alex.williamson@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Greg KH <gregkh@linuxfoundation.org>,
Sean Christopherson <seanjc@google.com>,
Roxana Bradescu <roxabee@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] kvm/vfio: avoid bouncing the mutex when adding and deleting groups
Date: Fri, 14 Jul 2023 13:31:56 -0600 [thread overview]
Message-ID: <20230714133156.3e584eab.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230714183800.3112449-2-dmitry.torokhov@gmail.com>
On Fri, 14 Jul 2023 11:37:57 -0700
Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> Stop taking kv->lock mutex in kvm_vfio_update_coherency() and instead
> call it with this mutex held: the callers of the function usually
> already have it taken (and released) before calling
> kvm_vfio_update_coherency(). This avoid bouncing the lock up and down.
>
> The exception is kvm_vfio_release() where we do not take the lock, but
> it is being executed when the very last reference to kvm_device is being
> dropped, so there are no concerns about concurrency.
>
> Suggested-by: Alex Williamson <alex.williamson@redhat.com>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
>
> v2: new patch.
>
> virt/kvm/vfio.c | 25 +++++++++----------------
> 1 file changed, 9 insertions(+), 16 deletions(-)
>
> diff --git a/virt/kvm/vfio.c b/virt/kvm/vfio.c
> index cd46d7ef98d6..9868e7ccb5fb 100644
> --- a/virt/kvm/vfio.c
> +++ b/virt/kvm/vfio.c
> @@ -122,8 +122,6 @@ static void kvm_vfio_update_coherency(struct kvm_device *dev)
> bool noncoherent = false;
> struct kvm_vfio_group *kvg;
>
> - mutex_lock(&kv->lock);
> -
> list_for_each_entry(kvg, &kv->group_list, node) {
> if (!kvm_vfio_file_enforced_coherent(kvg->file)) {
> noncoherent = true;
> @@ -139,8 +137,6 @@ static void kvm_vfio_update_coherency(struct kvm_device *dev)
> else
> kvm_arch_unregister_noncoherent_dma(dev->kvm);
> }
> -
> - mutex_unlock(&kv->lock);
> }
>
> static int kvm_vfio_group_add(struct kvm_device *dev, unsigned int fd)
> @@ -157,7 +153,7 @@ static int kvm_vfio_group_add(struct kvm_device *dev, unsigned int fd)
> /* Ensure the FD is a vfio group FD.*/
> if (!kvm_vfio_file_is_group(filp)) {
> ret = -EINVAL;
> - goto err_fput;
> + goto out_fput;
> }
>
> mutex_lock(&kv->lock);
> @@ -165,30 +161,27 @@ static int kvm_vfio_group_add(struct kvm_device *dev, unsigned int fd)
> list_for_each_entry(kvg, &kv->group_list, node) {
> if (kvg->file == filp) {
> ret = -EEXIST;
> - goto err_unlock;
> + goto out_unlock;
> }
> }
>
> kvg = kzalloc(sizeof(*kvg), GFP_KERNEL_ACCOUNT);
> if (!kvg) {
> ret = -ENOMEM;
> - goto err_unlock;
> + goto out_unlock;
> }
>
> - kvg->file = filp;
> + kvg->file = get_file(filp);
> list_add_tail(&kvg->node, &kv->group_list);
>
> kvm_arch_start_assignment(dev->kvm);
> kvm_vfio_file_set_kvm(kvg->file, dev->kvm);
> -
> - mutex_unlock(&kv->lock);
> -
> kvm_vfio_update_coherency(dev);
>
> - return 0;
> -err_unlock:
> + ret = 0;
Nit, let's initialize ret = 0 when it's declared to avoid this. Series
looks good to me otherwise. Thanks,
Alex
> +out_unlock:
> mutex_unlock(&kv->lock);
> -err_fput:
> +out_fput:
> fput(filp);
> return ret;
> }
> @@ -224,12 +217,12 @@ static int kvm_vfio_group_del(struct kvm_device *dev, unsigned int fd)
> break;
> }
>
> + kvm_vfio_update_coherency(dev);
> +
> mutex_unlock(&kv->lock);
>
> fdput(f);
>
> - kvm_vfio_update_coherency(dev);
> -
> return ret;
> }
>
prev parent reply other threads:[~2023-07-14 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 18:37 [PATCH v2 1/2] kvm/vfio: ensure kvg instance stays around in kvm_vfio_group_add() Dmitry Torokhov
2023-07-14 18:37 ` [PATCH v2 2/2] kvm/vfio: avoid bouncing the mutex when adding and deleting groups Dmitry Torokhov
2023-07-14 19:31 ` Alex Williamson [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=20230714133156.3e584eab.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=roxabee@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®