Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp6165661rwl; Wed, 22 Mar 2023 07:19:35 -0700 (PDT) X-Google-Smtp-Source: AK7set8k5ZUxxh9Eco32VrYfne6+Rr32YIt9gCptROLH2ofvRYo4MB+mN+hZtXqyMC+EHT40dKR/ X-Received: by 2002:a17:90b:3e89:b0:233:f393:f6cd with SMTP id rj9-20020a17090b3e8900b00233f393f6cdmr4263012pjb.5.1679494775073; Wed, 22 Mar 2023 07:19:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1679494775; cv=none; d=google.com; s=arc-20160816; b=AL7teypofDiB+DzqYQTXVcxRmnv7/OBLIwkQXwffgoJFtLtn325SR2xAToSIXkozed cR2gF2oZCt+0eDQf3Sux0HzSb5nmFstL52bp2ShakM+wmGUGBtl3/XKQxj+D7C7/MLhy iL/Y3quALwelYF+zG9tTeXlHulqaAEbESdUSgvW7n9KftAEXrMwr4n4i4k1mlNQvVlud jPuwvqVhPZ0y1FgTzO12GiDSlx56bFfo+77Dcz6liWjC5UoDZmORmW/iQpQcSbqN8kl7 C38WmFrvMBugYUpEvUFvHuQvG+l/EU0tAC27iuVx+mQIL91YvWTvLfvsSqXbBINR4td4 5DKw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=mewO7z5E5Yeya4ngQ8pJghMk9dN2fAZxntYD8VXxevA=; b=S22RwCFudmCmagN+KtB21a3JE4qOcfaHJi/d9Bbv73TfcTASrGKuNU9z3XBNnbj5Vg b6tFttmdseiq/CWare0Z6lj1ImiYXw+Ux9Fx3X37z1U3AzVHVkxKJoiMoDh33NORhYhP 24rpjqhmaP4goJfM4BCASRzGBdKU9ArXgVEft/qtw5ed++lR6V8HQ2K/FYgC6zMxo9IW /rn51DlEJkXk0ftYk5UYZ1Y3fRp0dRpCtM+nhyBah5XH1tgsYnGyyDQ8RT2WKvx/4w0F GfQaO0qjdYCaUpQojOUD1MUUYCY57t/3hUibTG6egvpN5IOaRreqXtiq8KayX8FaPogx s7yA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@daynix-com.20210112.gappssmtp.com header.s=20210112 header.b=t1XIEHys; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ix7-20020a170902f80700b0019e3ffa255asi15705951plb.184.2023.03.22.07.19.22; Wed, 22 Mar 2023 07:19:35 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@daynix-com.20210112.gappssmtp.com header.s=20210112 header.b=t1XIEHys; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231317AbjCVOKq (ORCPT + 99 others); Wed, 22 Mar 2023 10:10:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35246 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230525AbjCVOKo (ORCPT ); Wed, 22 Mar 2023 10:10:44 -0400 Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D5A625F525 for ; Wed, 22 Mar 2023 07:10:41 -0700 (PDT) Received: by mail-lf1-x132.google.com with SMTP id s8so23329854lfr.8 for ; Wed, 22 Mar 2023 07:10:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=daynix-com.20210112.gappssmtp.com; s=20210112; t=1679494240; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=mewO7z5E5Yeya4ngQ8pJghMk9dN2fAZxntYD8VXxevA=; b=t1XIEHyshK4KckxpJ/sI6CNpB9Amj1sdOGSbTJHAewHEQ83DG7/K/Ttl6p5T7YWtzg yAKBipgATNkKMyGbyBIvdxzU6J0EKi7BUPtJsBwyn16Zd8l+ZRfAUCNfbZ4n7/SVkP4s rErdNQojy4PxnkcAYMJOS6GL6z0VvW93Zws8ofS3TgTP4nxKpBS6eiAsNHKCFSKHRRjS M1gkVDvNC9sxfcNTORRXiIBo2e19HdDHdas3iOylTj4lRoT66hCicTpRVtUpeUbq7oZA /1GM5PqsGu8HufwPKhEV9nJH3NvxrSG8m9syY2FY0GOYsgO41RQBy8jk3gX4XG3IUP1A okvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679494240; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mewO7z5E5Yeya4ngQ8pJghMk9dN2fAZxntYD8VXxevA=; b=F+IkWveeNLspS5qAa4JuMcMQva88l0KHRZtFeTi3XleM1xuVzEcUxPp3oT6JgAvhVi HmU1FC5yAfk9Tt+/meyMTbIGphW8ZKH4aGE4Web/7G6xZCKzjYUvP/zOtVhkNRa/6oGq kO65fqjEV9j7msCPKyGXNolC+Si5TjSjNePIaodzUwtdm/Ybd4Vj56Uuq8AXNG9+SF/l Kl17ZZwVTPWPw0lWVLKcjeWO5Q54nZFkZUcC7bmg4eXfQuq6x+y0aPbOk/MOnkWwSmY1 3Ev+Bq2pXOXdDVwl6GuojHZiJwI3A2onYPEPJuXr1FQZFLuwZbA08ZzyWLv3O8ZhDBvd wvqg== X-Gm-Message-State: AO0yUKWk0DV8KScC9VIAMr8HxNWu+HSj9KsOAYYPptk9Twx/D8CnPxT+ U2Luw8Uj7QgtSBQRLZZ1tn/okg== X-Received: by 2002:ac2:5dc7:0:b0:4e8:43e2:a8 with SMTP id x7-20020ac25dc7000000b004e843e200a8mr2148310lfq.8.1679494239977; Wed, 22 Mar 2023 07:10:39 -0700 (PDT) Received: from vp-pc.. ([109.252.122.203]) by smtp.gmail.com with ESMTPSA id a9-20020a056512020900b004dc4e3f02aasm2621736lfo.53.2023.03.22.07.10.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Mar 2023 07:10:39 -0700 (PDT) From: Viktor Prutyanov To: mst@redhat.com, jasowang@redhat.com Cc: cohuck@redhat.com, pasic@linux.ibm.com, farman@linux.ibm.com, linux-s390@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, yan@daynix.com, viktor@daynix.com Subject: [PATCH v4] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support Date: Wed, 22 Mar 2023 17:10:31 +0300 Message-Id: <20230322141031.2211141-1-viktor@daynix.com> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org According to VirtIO spec v1.2, VIRTIO_F_NOTIFICATION_DATA feature indicates that the driver passes extra data along with the queue notifications. In a split queue case, the extra data is 16-bit available index. In a packed queue case, the extra data is 1-bit wrap counter and 15-bit available index. Add support for this feature for MMIO, channel I/O and modern PCI transports. Signed-off-by: Viktor Prutyanov --- v4: remove VP_NOTIFY macro and legacy PCI support, add virtio_ccw_kvm_notify_with_data to virtio_ccw v3: support feature in virtio_ccw, remove VM_NOTIFY, use avail_idx_shadow, remove byte swap, rename to vring_notification_data v2: reject the feature in virtio_ccw, replace __le32 with u32 Tested with disabled VIRTIO_F_NOTIFICATION_DATA on qemu-system-s390x (virtio-blk-ccw), qemu-system-riscv64 (virtio-blk-device, virtio-rng-device), qemu-system-x86_64 (virtio-blk-pci, virtio-net-pci) to make sure nothing is broken. Tested with enabled VIRTIO_F_NOTIFICATION_DATA on 64-bit RISC-V Linux and my hardware implementation of virtio-rng. drivers/s390/virtio/virtio_ccw.c | 19 ++++++++++++++++--- drivers/virtio/virtio_mmio.c | 14 +++++++++++++- drivers/virtio/virtio_pci_modern.c | 13 ++++++++++++- drivers/virtio/virtio_ring.c | 17 +++++++++++++++++ include/linux/virtio_ring.h | 2 ++ include/uapi/linux/virtio_config.h | 6 ++++++ 6 files changed, 66 insertions(+), 5 deletions(-) diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c index 954fc31b4bc7..3619676effb8 100644 --- a/drivers/s390/virtio/virtio_ccw.c +++ b/drivers/s390/virtio/virtio_ccw.c @@ -391,7 +391,7 @@ static void virtio_ccw_drop_indicator(struct virtio_ccw_device *vcdev, ccw_device_dma_free(vcdev->cdev, thinint_area, sizeof(*thinint_area)); } -static bool virtio_ccw_kvm_notify(struct virtqueue *vq) +static inline bool virtio_ccw_do_kvm_notify(struct virtqueue *vq, u32 data) { struct virtio_ccw_vq_info *info = vq->priv; struct virtio_ccw_device *vcdev; @@ -402,12 +402,22 @@ static bool virtio_ccw_kvm_notify(struct virtqueue *vq) BUILD_BUG_ON(sizeof(struct subchannel_id) != sizeof(unsigned int)); info->cookie = kvm_hypercall3(KVM_S390_VIRTIO_CCW_NOTIFY, *((unsigned int *)&schid), - vq->index, info->cookie); + data, info->cookie); if (info->cookie < 0) return false; return true; } +static bool virtio_ccw_kvm_notify(struct virtqueue *vq) +{ + return virtio_ccw_do_kvm_notify(vq, vq->index); +} + +static bool virtio_ccw_kvm_notify_with_data(struct virtqueue *vq) +{ + return virtio_ccw_do_kvm_notify(vq, vring_notification_data(vq)); +} + static int virtio_ccw_read_vq_conf(struct virtio_ccw_device *vcdev, struct ccw1 *ccw, int index) { @@ -501,6 +511,9 @@ static struct virtqueue *virtio_ccw_setup_vq(struct virtio_device *vdev, u64 queue; unsigned long flags; bool may_reduce; + bool (*notify)(struct virtqueue *vq) = __virtio_test_bit(vdev, + VIRTIO_F_NOTIFICATION_DATA) ? + virtio_ccw_kvm_notify_with_data : virtio_ccw_kvm_notify; /* Allocate queue. */ info = kzalloc(sizeof(struct virtio_ccw_vq_info), GFP_KERNEL); @@ -524,7 +537,7 @@ static struct virtqueue *virtio_ccw_setup_vq(struct virtio_device *vdev, may_reduce = vcdev->revision > 0; vq = vring_create_virtqueue(i, info->num, KVM_VIRTIO_CCW_RING_ALIGN, vdev, true, may_reduce, ctx, - virtio_ccw_kvm_notify, callback, name); + notify, callback, name); if (!vq) { /* For now, we fail if we can't get the requested size. */ diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c index 3ff746e3f24a..7c16e622c33d 100644 --- a/drivers/virtio/virtio_mmio.c +++ b/drivers/virtio/virtio_mmio.cv @@ -285,6 +285,16 @@ static bool vm_notify(struct virtqueue *vq) return true; } +static bool vm_notify_with_data(struct virtqueue *vq) +{ + struct virtio_mmio_device *vm_dev = to_virtio_mmio_device(vq->vdev); + u32 data = vring_notification_data(vq); + + writel(data, vm_dev->base + VIRTIO_MMIO_QUEUE_NOTIFY); + + return true; +} + /* Notify all virtqueues on an interrupt. */ static irqreturn_t vm_interrupt(int irq, void *opaque) { @@ -368,6 +378,8 @@ static struct virtqueue *vm_setup_vq(struct virtio_device *vdev, unsigned int in unsigned long flags; unsigned int num; int err; + bool (*notify)(struct virtqueue *vq) = __virtio_test_bit(vdev, + VIRTIO_F_NOTIFICATION_DATA) ? vm_notify_with_data : vm_notify; if (!name) return NULL; @@ -397,7 +409,7 @@ static struct virtqueue *vm_setup_vq(struct virtio_device *vdev, unsigned int in /* Create the vring */ vq = vring_create_virtqueue(index, num, VIRTIO_MMIO_VRING_ALIGN, vdev, - true, true, ctx, vm_notify, callback, name); + true, true, ctx, notify, callback, name); if (!vq) { err = -ENOMEM; goto error_new_virtqueue; diff --git a/drivers/virtio/virtio_pci_modern.c b/drivers/virtio/virtio_pci_modern.c index 9e496e288cfa..9cc56f463dba 100644 --- a/drivers/virtio/virtio_pci_modern.c +++ b/drivers/virtio/virtio_pci_modern.c @@ -288,6 +288,15 @@ static u16 vp_config_vector(struct virtio_pci_device *vp_dev, u16 vector) return vp_modern_config_vector(&vp_dev->mdev, vector); } +static bool vp_notify_with_data(struct virtqueue *vq) +{ + u32 data = vring_notification_data(vq); + + iowrite32(data, (void __iomem *)vq->priv); + + return true; +} + static struct virtqueue *setup_vq(struct virtio_pci_device *vp_dev, struct virtio_pci_vq_info *info, unsigned int index, @@ -301,6 +310,8 @@ static struct virtqueue *setup_vq(struct virtio_pci_device *vp_dev, struct virtqueue *vq; u16 num; int err; + bool (*notify)(struct virtqueue *vq) = __virtio_test_bit(&vp_dev->vdev, + VIRTIO_F_NOTIFICATION_DATA) ? vp_notify_with_data : vp_notify; if (index >= vp_modern_get_num_queues(mdev)) return ERR_PTR(-EINVAL); @@ -321,7 +332,7 @@ static struct virtqueue *setup_vq(struct virtio_pci_device *vp_dev, vq = vring_create_virtqueue(index, num, SMP_CACHE_BYTES, &vp_dev->vdev, true, true, ctx, - vp_notify, callback, name); + notify, callback, name); if (!vq) return ERR_PTR(-ENOMEM); diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c index 4c3bb0ddeb9b..837875cc3190 100644 --- a/drivers/virtio/virtio_ring.c +++ b/drivers/virtio/virtio_ring.c @@ -2752,6 +2752,21 @@ void vring_del_virtqueue(struct virtqueue *_vq) } EXPORT_SYMBOL_GPL(vring_del_virtqueue); +u32 vring_notification_data(struct virtqueue *_vq) +{ + struct vring_virtqueue *vq = to_vvq(_vq); + u16 next; + + if (vq->packed_ring) + next = (vq->packed.next_avail_idx & ~(1 << 15)) | + vq->packed.avail_wrap_counter << 15; + else + next = vq->split.avail_idx_shadow; + + return next << 16 | _vq->index; +} +EXPORT_SYMBOL_GPL(vring_notification_data); + /* Manipulates transport-specific feature bits. */ void vring_transport_features(struct virtio_device *vdev) { @@ -2771,6 +2786,8 @@ void vring_transport_features(struct virtio_device *vdev) break; case VIRTIO_F_ORDER_PLATFORM: break; + case VIRTIO_F_NOTIFICATION_DATA: + break; default: /* We don't understand this bit. */ __virtio_clear_bit(vdev, i); diff --git a/include/linux/virtio_ring.h b/include/linux/virtio_ring.h index 8b95b69ef694..2550c9170f4f 100644 --- a/include/linux/virtio_ring.h +++ b/include/linux/virtio_ring.h @@ -117,4 +117,6 @@ void vring_del_virtqueue(struct virtqueue *vq); void vring_transport_features(struct virtio_device *vdev); irqreturn_t vring_interrupt(int irq, void *_vq); + +u32 vring_notification_data(struct virtqueue *_vq); #endif /* _LINUX_VIRTIO_RING_H */ diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h index 3c05162bc988..2c712c654165 100644 --- a/include/uapi/linux/virtio_config.h +++ b/include/uapi/linux/virtio_config.h @@ -99,6 +99,12 @@ */ #define VIRTIO_F_SR_IOV 37 +/* + * This feature indicates that the driver passes extra data (besides + * identifying the virtqueue) in its device notifications. + */ +#define VIRTIO_F_NOTIFICATION_DATA 38 + /* * This feature indicates that the driver can reset a queue individually. */ -- 2.35.1