From: Jason Wang <jasowang@redhat.com>
To: Xie Yongji <xieyongji@bytedance.com>,
mst@redhat.com, stefanha@redhat.com, sgarzare@redhat.com,
parav@nvidia.com, bob.liu@oracle.com, hch@infradead.org,
rdunlap@infradead.org, willy@infradead.org,
viro@zeniv.linux.org.uk, axboe@kernel.dk, bcrl@kvack.org,
corbet@lwn.net, mika.penttila@nextfour.com,
dan.carpenter@oracle.com
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, kvm@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v5 10/11] vduse: Add config interrupt support
Date: Wed, 24 Mar 2021 12:45:35 +0800 [thread overview]
Message-ID: <9a2835b1-1f0e-5646-6c77-524e6ccdc613@redhat.com> (raw)
In-Reply-To: <20210315053721.189-11-xieyongji@bytedance.com>
在 2021/3/15 下午1:37, Xie Yongji 写道:
> This patch introduces a new ioctl VDUSE_INJECT_CONFIG_IRQ
> to support injecting config interrupt.
>
> Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
I suggest to squash this into path 9.
Other looks good.
Thanks
> ---
> drivers/vdpa/vdpa_user/vduse_dev.c | 24 +++++++++++++++++++++++-
> include/uapi/linux/vduse.h | 3 +++
> 2 files changed, 26 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vdpa/vdpa_user/vduse_dev.c b/drivers/vdpa/vdpa_user/vduse_dev.c
> index 07d0ae92d470..cc12b58bdc09 100644
> --- a/drivers/vdpa/vdpa_user/vduse_dev.c
> +++ b/drivers/vdpa/vdpa_user/vduse_dev.c
> @@ -64,6 +64,8 @@ struct vduse_dev {
> struct list_head send_list;
> struct list_head recv_list;
> struct list_head list;
> + struct vdpa_callback config_cb;
> + spinlock_t irq_lock;
> bool connected;
> int minor;
> u16 vq_size_max;
> @@ -439,6 +441,11 @@ static void vduse_dev_reset(struct vduse_dev *dev)
> vduse_domain_reset_bounce_map(dev->domain);
> vduse_dev_update_iotlb(dev, 0ULL, ULLONG_MAX);
>
> + spin_lock(&dev->irq_lock);
> + dev->config_cb.callback = NULL;
> + dev->config_cb.private = NULL;
> + spin_unlock(&dev->irq_lock);
> +
> for (i = 0; i < dev->vq_num; i++) {
> struct vduse_virtqueue *vq = &dev->vqs[i];
>
> @@ -557,7 +564,12 @@ static int vduse_vdpa_set_features(struct vdpa_device *vdpa, u64 features)
> static void vduse_vdpa_set_config_cb(struct vdpa_device *vdpa,
> struct vdpa_callback *cb)
> {
> - /* We don't support config interrupt */
> + struct vduse_dev *dev = vdpa_to_vduse(vdpa);
> +
> + spin_lock(&dev->irq_lock);
> + dev->config_cb.callback = cb->callback;
> + dev->config_cb.private = cb->private;
> + spin_unlock(&dev->irq_lock);
> }
>
> static u16 vduse_vdpa_get_vq_num_max(struct vdpa_device *vdpa)
> @@ -842,6 +854,15 @@ static long vduse_dev_ioctl(struct file *file, unsigned int cmd,
> ret = 0;
> queue_work(vduse_irq_wq, &dev->vqs[arg].inject);
> break;
> + case VDUSE_INJECT_CONFIG_IRQ:
> + ret = -EINVAL;
> + spin_lock_irq(&dev->irq_lock);
> + if (dev->config_cb.callback) {
> + dev->config_cb.callback(dev->config_cb.private);
> + ret = 0;
> + }
> + spin_unlock_irq(&dev->irq_lock);
> + break;
> default:
> ret = -ENOIOCTLCMD;
> break;
> @@ -918,6 +939,7 @@ static struct vduse_dev *vduse_dev_create(void)
> INIT_LIST_HEAD(&dev->send_list);
> INIT_LIST_HEAD(&dev->recv_list);
> atomic64_set(&dev->msg_unique, 0);
> + spin_lock_init(&dev->irq_lock);
>
> init_waitqueue_head(&dev->waitq);
>
> diff --git a/include/uapi/linux/vduse.h b/include/uapi/linux/vduse.h
> index 37f7d7059aa8..337e766f5622 100644
> --- a/include/uapi/linux/vduse.h
> +++ b/include/uapi/linux/vduse.h
> @@ -150,4 +150,7 @@ struct vduse_vq_eventfd {
> /* Inject an interrupt for specific virtqueue */
> #define VDUSE_INJECT_VQ_IRQ _IO(VDUSE_BASE, 0x05)
>
> +/* Inject a config interrupt */
> +#define VDUSE_INJECT_CONFIG_IRQ _IO(VDUSE_BASE, 0x06)
> +
> #endif /* _UAPI_VDUSE_H_ */
next prev parent reply other threads:[~2021-03-24 4:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 5:37 [PATCH v5 00/11] Introduce VDUSE - vDPA Device in Userspace Xie Yongji
2021-03-15 5:37 ` [PATCH v5 01/11] file: Export __receive_fd() to modules Xie Yongji
2021-03-15 9:08 ` Christoph Hellwig
2021-03-15 9:46 ` Yongji Xie
2021-03-15 14:44 ` Christian Brauner
2021-03-16 2:48 ` Yongji Xie
2021-03-25 8:23 ` Christoph Hellwig
2021-03-25 11:04 ` Yongji Xie
2021-03-15 5:37 ` [PATCH v5 02/11] eventfd: Increase the recursion depth of eventfd_signal() Xie Yongji
2021-03-15 5:37 ` [PATCH v5 03/11] vhost-vdpa: protect concurrent access to vhost device iotlb Xie Yongji
2021-03-23 3:02 ` Jason Wang
2021-03-23 7:25 ` Yongji Xie
2021-03-25 11:08 ` Stefano Garzarella
2021-03-15 5:37 ` [PATCH v5 04/11] vhost-iotlb: Add an opaque pointer for vhost IOTLB Xie Yongji
2021-03-15 5:37 ` [PATCH v5 05/11] vdpa: Add an opaque pointer for vdpa_config_ops.dma_map() Xie Yongji
2021-03-15 5:37 ` [PATCH v5 06/11] vdpa: factor out vhost_vdpa_pa_map() Xie Yongji
2021-03-23 3:09 ` Jason Wang
2021-03-15 5:37 ` [PATCH v5 07/11] vdpa: Support transferring virtual addressing during DMA mapping Xie Yongji
2021-03-23 3:13 ` Jason Wang
2021-03-23 7:26 ` Yongji Xie
2021-03-15 5:37 ` [PATCH v5 08/11] vduse: Implement an MMU-based IOMMU driver Xie Yongji
2021-03-24 3:54 ` Jason Wang
2021-03-24 7:39 ` Yongji Xie
2021-03-25 4:52 ` Jason Wang
2021-03-25 7:38 ` Yongji Xie
2021-03-26 4:26 ` Jason Wang
2021-03-26 5:14 ` Yongji Xie
[not found] ` <75e3b941-dfd2-ebbc-d752-8f25c1f14cab@redhat.com>
2021-03-26 6:56 ` Yongji Xie
2021-03-26 7:36 ` Jason Wang
2021-03-15 5:37 ` [PATCH v5 09/11] vduse: Introduce VDUSE - vDPA Device in Userspace Xie Yongji
2021-03-24 4:43 ` Jason Wang
2021-03-24 8:55 ` Yongji Xie
2021-03-25 6:30 ` Jason Wang
2021-03-25 7:47 ` Yongji Xie
2021-03-15 5:37 ` [PATCH v5 10/11] vduse: Add config interrupt support Xie Yongji
2021-03-24 4:45 ` Jason Wang [this message]
2021-03-24 8:56 ` Yongji Xie
2021-03-15 5:37 ` [PATCH v5 11/11] Documentation: Add documentation for VDUSE Xie Yongji
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=9a2835b1-1f0e-5646-6c77-524e6ccdc613@redhat.com \
--to=jasowang@redhat.com \
--cc=axboe@kernel.dk \
--cc=bcrl@kvack.org \
--cc=bob.liu@oracle.com \
--cc=corbet@lwn.net \
--cc=dan.carpenter@oracle.com \
--cc=hch@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mika.penttila@nextfour.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=rdunlap@infradead.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).