Linux virtualization list
 help / color / mirror / Atom feed
From: Stefano Garzarella <sgarzare@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
	Max Gurtovoy <mgurtovoy@nvidia.com>,
	kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Xie Yongji <xieyongji@bytedance.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH RFC v2 02/10] vringh: add 'iotlb_lock' to synchronize iotlb accesses
Date: Fri, 29 Jan 2021 10:18:50 +0100	[thread overview]
Message-ID: <20210129091850.gatf3ih3knw2p4l4@steredhat> (raw)
In-Reply-To: <017f6e69-b2ec-aed0-5920-a389199e4cf9@redhat.com>

On Fri, Jan 29, 2021 at 03:43:40PM +0800, Jason Wang wrote:
>
>On 2021/1/28 下午10:41, Stefano Garzarella wrote:
>>Usually iotlb accesses are synchronized with a spinlock.
>>Let's request it as a new parameter in vringh_set_iotlb() and
>>hold it when we navigate the iotlb in iotlb_translate() to avoid
>>race conditions with any new additions/deletions of ranges from
>>the ioltb.
>
>
>Patch looks fine but I wonder if this is the best approach comparing 
>to do locking by the caller.

Initially I tried to hold the lock in the vdpasim_blk_work(), but since
we have a lot of different functions for vringh, I opted to take the 
lock at the beginning and release it at the end.
Also because several times I went to see if that call used 
iotlb_translate or not.

This could be a problem for example if we have multiple workers to 
handle multiple queues.

Also, some functions are quite long (e.g. vringh_getdesc_iotlb) and 
holding the lock for that long could reduce parallelism.

For these reasons I thought it was better to hide everything from the 
caller who doesn't have to worry about which function calls 
iotlb_translate() and thus hold the lock.

Thanks,
Stefano

>
>Thanks
>
>
>>
>>Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
>>---
>>  include/linux/vringh.h           | 6 +++++-
>>  drivers/vdpa/vdpa_sim/vdpa_sim.c | 3 ++-
>>  drivers/vhost/vringh.c           | 9 ++++++++-
>>  3 files changed, 15 insertions(+), 3 deletions(-)
>>
>>diff --git a/include/linux/vringh.h b/include/linux/vringh.h
>>index 59bd50f99291..9c077863c8f6 100644
>>--- a/include/linux/vringh.h
>>+++ b/include/linux/vringh.h
>>@@ -46,6 +46,9 @@ struct vringh {
>>  	/* IOTLB for this vring */
>>  	struct vhost_iotlb *iotlb;
>>+	/* spinlock to synchronize IOTLB accesses */
>>+	spinlock_t *iotlb_lock;
>>+
>>  	/* The function to call to notify the guest about added buffers */
>>  	void (*notify)(struct vringh *);
>>  };
>>@@ -258,7 +261,8 @@ static inline __virtio64 cpu_to_vringh64(const struct vringh *vrh, u64 val)
>>  #if IS_REACHABLE(CONFIG_VHOST_IOTLB)
>>-void vringh_set_iotlb(struct vringh *vrh, struct vhost_iotlb *iotlb);
>>+void vringh_set_iotlb(struct vringh *vrh, struct vhost_iotlb *iotlb,
>>+		      spinlock_t *iotlb_lock);
>>  int vringh_init_iotlb(struct vringh *vrh, u64 features,
>>  		      unsigned int num, bool weak_barriers,
>>diff --git a/drivers/vdpa/vdpa_sim/vdpa_sim.c b/drivers/vdpa/vdpa_sim/vdpa_sim.c
>>index 2183a833fcf4..53238989713d 100644
>>--- a/drivers/vdpa/vdpa_sim/vdpa_sim.c
>>+++ b/drivers/vdpa/vdpa_sim/vdpa_sim.c
>>@@ -284,7 +284,8 @@ struct vdpasim *vdpasim_create(struct vdpasim_dev_attr *dev_attr)
>>  		goto err_iommu;
>>  	for (i = 0; i < dev_attr->nvqs; i++)
>>-		vringh_set_iotlb(&vdpasim->vqs[i].vring, vdpasim->iommu);
>>+		vringh_set_iotlb(&vdpasim->vqs[i].vring, vdpasim->iommu,
>>+				 &vdpasim->iommu_lock);
>>  	ret = iova_cache_get();
>>  	if (ret)
>>diff --git a/drivers/vhost/vringh.c b/drivers/vhost/vringh.c
>>index 85d85faba058..f68122705719 100644
>>--- a/drivers/vhost/vringh.c
>>+++ b/drivers/vhost/vringh.c
>>@@ -1074,6 +1074,8 @@ static int iotlb_translate(const struct vringh *vrh,
>>  	int ret = 0;
>>  	u64 s = 0;
>>+	spin_lock(vrh->iotlb_lock);
>>+
>>  	while (len > s) {
>>  		u64 size, pa, pfn;
>>@@ -1103,6 +1105,8 @@ static int iotlb_translate(const struct vringh *vrh,
>>  		++ret;
>>  	}
>>+	spin_unlock(vrh->iotlb_lock);
>>+
>>  	return ret;
>>  }
>>@@ -1262,10 +1266,13 @@ EXPORT_SYMBOL(vringh_init_iotlb);
>>   * vringh_set_iotlb - initialize a vringh for a ring with IOTLB.
>>   * @vrh: the vring
>>   * @iotlb: iotlb associated with this vring
>>+ * @iotlb_lock: spinlock to synchronize the iotlb accesses
>>   */
>>-void vringh_set_iotlb(struct vringh *vrh, struct vhost_iotlb *iotlb)
>>+void vringh_set_iotlb(struct vringh *vrh, struct vhost_iotlb *iotlb,
>>+		      spinlock_t *iotlb_lock)
>>  {
>>  	vrh->iotlb = iotlb;
>>+	vrh->iotlb_lock = iotlb_lock;
>>  }
>>  EXPORT_SYMBOL(vringh_set_iotlb);
>

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2021-01-29  9:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 14:41 [PATCH RFC v2 00/10] vdpa: add vdpa simulator for block device Stefano Garzarella
2021-01-28 14:41 ` [PATCH RFC v2 01/10] vdpa_sim: use iova module to allocate IOVA addresses Stefano Garzarella
2021-01-28 14:41 ` [PATCH RFC v2 02/10] vringh: add 'iotlb_lock' to synchronize iotlb accesses Stefano Garzarella
2021-01-29  7:43   ` Jason Wang
2021-01-29  9:18     ` Stefano Garzarella [this message]
2021-02-01  6:31       ` Jason Wang
2021-01-28 14:41 ` [PATCH RFC v2 03/10] vringh: reset kiov 'consumed' field in __vringh_iov() Stefano Garzarella
2021-02-01  5:40   ` Jason Wang
2021-02-01 10:21     ` Stefano Garzarella
2021-02-02  3:26       ` Jason Wang
2021-01-28 14:41 ` [PATCH RFC v2 04/10] vringh: implement vringh_kiov_advance() Stefano Garzarella
2021-02-01  5:43   ` Jason Wang
2021-02-01 10:23     ` Stefano Garzarella
2021-01-28 14:41 ` [PATCH RFC v2 05/10] vringh: add vringh_kiov_length() helper Stefano Garzarella
2021-02-01  5:46   ` Jason Wang
2021-01-28 14:41 ` [PATCH RFC v2 06/10] vdpa_sim: cleanup kiovs in vdpasim_free() Stefano Garzarella
2021-02-01  5:47   ` Jason Wang
2021-01-28 14:41 ` [PATCH RFC v2 07/10] vdpa: Remove the restriction that only supports virtio-net devices Stefano Garzarella
2021-01-28 14:41 ` [PATCH RFC v2 08/10] vdpa: add vdpa simulator for block device Stefano Garzarella
2021-02-01  5:50   ` Jason Wang
     [not found]   ` <e8f97ea2-d179-de37-a0ea-b2858510f3ce@nvidia.com>
2021-02-01  8:29     ` Stefano Garzarella
2021-02-02  9:34   ` Stefan Hajnoczi
2021-02-02 15:49     ` Stefano Garzarella
2021-02-03 16:45       ` Stefan Hajnoczi
2021-02-04  8:02         ` Stefano Garzarella
2021-01-28 14:41 ` [PATCH RFC v2 09/10] vdpa_sim_blk: implement ramdisk behaviour Stefano Garzarella
2021-02-01  6:03   ` Jason Wang
2021-02-02  9:41   ` Stefan Hajnoczi
2021-01-28 14:41 ` [PATCH RFC v2 10/10] vdpa_sim_blk: handle VIRTIO_BLK_T_GET_ID Stefano Garzarella
2021-02-01  6:04   ` Jason Wang
2021-02-02  9:44   ` Stefan Hajnoczi

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=20210129091850.gatf3ih3knw2p4l4@steredhat \
    --to=sgarzare@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=mgurtovoy@nvidia.com \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xieyongji@bytedance.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