From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="U+1FHY37" Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1726E10EF for ; Thu, 30 Nov 2023 01:46:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1701337566; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=PfGI1qlZAEAF2BhJp3RmJxUya50qDURSNVaHY6y9EXQ=; b=U+1FHY37/Pn3SjfZwwZL8EhYDSM0wvCGofnyA465OdN7FFx5iRcIoaD1pY5JJM3NpwcGVi MzC8tWJ/jQfQB9BtEbaBirpX0ZYKXlDiwBBmKMmCywA1H55DcVxGEEloAcdbOx9w7TRyH+ xVDpsFE9IGuwER4tCijK8E0TS58QlBc= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-504-yCboAz6BNDODXCRzP19AgA-1; Thu, 30 Nov 2023 04:46:04 -0500 X-MC-Unique: yCboAz6BNDODXCRzP19AgA-1 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-332ee20a3f0so815733f8f.0 for ; Thu, 30 Nov 2023 01:46:04 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701337563; x=1701942363; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=PfGI1qlZAEAF2BhJp3RmJxUya50qDURSNVaHY6y9EXQ=; b=h0bE05/a9OL17qZbJHMTUN1XVKIP1NRbrokEJkfxdIUTSYdXEX9R1fTq7Bhwj4ibgZ dA9wvknQghRf3hD3Jq9x/C/HRvdH96OT59D53gTgPqXt4AF5Yo9KH0mSyZeeSNKdOtSa 6Y60Yf+N1apWA/8jyn3Qwy5W38sijwM9fbXR7Nc+LsQfvVqC9DTKmNx0kGr05aVdIZtc uE1TSduR1E4NRFFFJZa2diZziUK65o5SXPHVxdBxOm2Z2A1sHiOxszkqVVVV2ny4t0WG Vd0rJkb1qOK0CPmoQKF/vCtlOEjYJNLV39ItzdmC8gJD6q6Vybz6E4GS/zQsaYUzybHb H11A== X-Gm-Message-State: AOJu0Yz92thoP1Ju6KSTyMdE41t+EfdmIl3HOO92EP7OjzMQw13V1qvJ Txk7B+EmrJMPq6MvYf4eIAsgEKAAQzrU5VeLpuAg3wYbEs5LJRhM3My0jWPt6f+T2ucvI4TdHQ7 2EWE5H3U4txqIiiuz X-Received: by 2002:adf:f18a:0:b0:333:2003:f8d5 with SMTP id h10-20020adff18a000000b003332003f8d5mr1300594wro.47.1701337563322; Thu, 30 Nov 2023 01:46:03 -0800 (PST) X-Google-Smtp-Source: AGHT+IFZ1YqAf91AEdYFb/UmG1d2aec7j4UFFqWCYZRHFF8ZmzzWbiemhO2JFaP7Qe8H76kv8gs1Wg== X-Received: by 2002:adf:f18a:0:b0:333:2003:f8d5 with SMTP id h10-20020adff18a000000b003332003f8d5mr1300567wro.47.1701337562911; Thu, 30 Nov 2023 01:46:02 -0800 (PST) Received: from redhat.com ([2.55.10.128]) by smtp.gmail.com with ESMTPSA id t3-20020adfe443000000b00332fcdafc22sm1036634wrm.70.2023.11.30.01.46.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Nov 2023 01:46:02 -0800 (PST) Date: Thu, 30 Nov 2023 04:45:58 -0500 From: "Michael S. Tsirkin" To: Xuan Zhuo Cc: virtualization@lists.linux-foundation.org, Jason Wang , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Alexei Starovoitov , Daniel Borkmann , Jesper Dangaard Brouer , John Fastabend , netdev@vger.kernel.org, bpf@vger.kernel.org, Christoph Hellwig Subject: Re: [PATCH vhost v13 11/12] virtio_ring: introduce dma sync api for virtqueue Message-ID: <20231130044512-mutt-send-email-mst@kernel.org> References: <20230810123057.43407-1-xuanzhuo@linux.alibaba.com> <20230810123057.43407-12-xuanzhuo@linux.alibaba.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230810123057.43407-12-xuanzhuo@linux.alibaba.com> On Thu, Aug 10, 2023 at 08:30:56PM +0800, Xuan Zhuo wrote: > These API has been introduced: > > * virtqueue_dma_need_sync > * virtqueue_dma_sync_single_range_for_cpu > * virtqueue_dma_sync_single_range_for_device > > These APIs can be used together with the premapped mechanism to sync the > DMA address. > > Signed-off-by: Xuan Zhuo > --- > drivers/virtio/virtio_ring.c | 76 ++++++++++++++++++++++++++++++++++++ > include/linux/virtio.h | 8 ++++ > 2 files changed, 84 insertions(+) > > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c > index 916479c9c72c..81ecb29c88f1 100644 > --- a/drivers/virtio/virtio_ring.c > +++ b/drivers/virtio/virtio_ring.c > @@ -3175,4 +3175,80 @@ int virtqueue_dma_mapping_error(struct virtqueue *_vq, dma_addr_t addr) > } > EXPORT_SYMBOL_GPL(virtqueue_dma_mapping_error); > > +/** > + * virtqueue_dma_need_sync - check a dma address needs sync > + * @_vq: the struct virtqueue we're talking about. > + * @addr: DMA address > + * > + * Check if the dma address mapped by the virtqueue_dma_map_* APIs needs to be > + * synchronized > + * > + * return bool > + */ > +bool virtqueue_dma_need_sync(struct virtqueue *_vq, dma_addr_t addr) > +{ > + struct vring_virtqueue *vq = to_vvq(_vq); > + > + if (!vq->use_dma_api) > + return false; > + > + return dma_need_sync(vring_dma_dev(vq), addr); > +} > +EXPORT_SYMBOL_GPL(virtqueue_dma_need_sync); > + > +/** > + * virtqueue_dma_sync_single_range_for_cpu - dma sync for cpu > + * @_vq: the struct virtqueue we're talking about. > + * @addr: DMA address > + * @offset: DMA address offset > + * @size: buf size for sync > + * @dir: DMA direction > + * > + * Before calling this function, use virtqueue_dma_need_sync() to confirm that > + * the DMA address really needs to be synchronized > + * > + */ > +void virtqueue_dma_sync_single_range_for_cpu(struct virtqueue *_vq, > + dma_addr_t addr, > + unsigned long offset, size_t size, > + enum dma_data_direction dir) > +{ > + struct vring_virtqueue *vq = to_vvq(_vq); > + struct device *dev = vring_dma_dev(vq); > + > + if (!vq->use_dma_api) > + return; > + > + dma_sync_single_range_for_cpu(dev, addr, offset, size, > + DMA_BIDIRECTIONAL); > +} Why did you use DMA_BIDIRECTIONAL here? Why is "dir" ignored? > +EXPORT_SYMBOL_GPL(virtqueue_dma_sync_single_range_for_cpu); > + > +/** > + * virtqueue_dma_sync_single_range_for_device - dma sync for device > + * @_vq: the struct virtqueue we're talking about. > + * @addr: DMA address > + * @offset: DMA address offset > + * @size: buf size for sync > + * @dir: DMA direction > + * > + * Before calling this function, use virtqueue_dma_need_sync() to confirm that > + * the DMA address really needs to be synchronized > + */ > +void virtqueue_dma_sync_single_range_for_device(struct virtqueue *_vq, > + dma_addr_t addr, > + unsigned long offset, size_t size, > + enum dma_data_direction dir) > +{ > + struct vring_virtqueue *vq = to_vvq(_vq); > + struct device *dev = vring_dma_dev(vq); > + > + if (!vq->use_dma_api) > + return; > + > + dma_sync_single_range_for_device(dev, addr, offset, size, > + DMA_BIDIRECTIONAL); > +} > +EXPORT_SYMBOL_GPL(virtqueue_dma_sync_single_range_for_device); > + > MODULE_LICENSE("GPL"); same question here. > diff --git a/include/linux/virtio.h b/include/linux/virtio.h > index 79e3c74391e0..1311a7fbe675 100644 > --- a/include/linux/virtio.h > +++ b/include/linux/virtio.h > @@ -220,4 +220,12 @@ void virtqueue_dma_unmap_single_attrs(struct virtqueue *_vq, dma_addr_t addr, > size_t size, enum dma_data_direction dir, > unsigned long attrs); > int virtqueue_dma_mapping_error(struct virtqueue *_vq, dma_addr_t addr); > + > +bool virtqueue_dma_need_sync(struct virtqueue *_vq, dma_addr_t addr); > +void virtqueue_dma_sync_single_range_for_cpu(struct virtqueue *_vq, dma_addr_t addr, > + unsigned long offset, size_t size, > + enum dma_data_direction dir); > +void virtqueue_dma_sync_single_range_for_device(struct virtqueue *_vq, dma_addr_t addr, > + unsigned long offset, size_t size, > + enum dma_data_direction dir); > #endif /* _LINUX_VIRTIO_H */ > -- > 2.32.0.3.g01195cf9f