From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8B7E8C6FD1D for ; Tue, 21 Mar 2023 16:22:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229906AbjCUQW4 (ORCPT ); Tue, 21 Mar 2023 12:22:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54112 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229475AbjCUQWy (ORCPT ); Tue, 21 Mar 2023 12:22:54 -0400 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 D3F6018B12 for ; Tue, 21 Mar 2023 09:22:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679415727; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lgoaZPNV6QFiAZ6BoiXCSnPeZXlIYAThltxiCwI3A8Q=; b=EOLcc6/WAwnTDHxxfQUjO00LgUKQISUjnZI/ea0ZJ8yNS90IrTwos5KV14q6egIB9ZDcw+ s4WGIFWldEuU/vG6nC1ADIw6NeIBhN/FM1YA+mV6WqIV9VC5AcOPhMN+iO0efs4dgfnzGf WWqX/7T/YeOMqbtxwmbKj1+mjvy+zeE= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-182-lZh2iYaPNROe8ncvNmm22g-1; Tue, 21 Mar 2023 12:22:01 -0400 X-MC-Unique: lZh2iYaPNROe8ncvNmm22g-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B26391008139; Tue, 21 Mar 2023 16:22:00 +0000 (UTC) Received: from localhost (unknown [10.39.193.206]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 48CDD140E960; Tue, 21 Mar 2023 16:22:00 +0000 (UTC) From: Cornelia Huck To: "Michael S. Tsirkin" Cc: Viktor Prutyanov , jasowang@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 Subject: Re: [PATCH v3] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support In-Reply-To: <20230321115854-mutt-send-email-mst@kernel.org> Organization: Red Hat GmbH References: <20230321134410.2097163-1-viktor@daynix.com> <87h6uem9qc.fsf@redhat.com> <87bkkmm89a.fsf@redhat.com> <20230321115854-mutt-send-email-mst@kernel.org> User-Agent: Notmuch/0.37 (https://notmuchmail.org) Date: Tue, 21 Mar 2023 17:21:59 +0100 Message-ID: <878rfqm5w8.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 21 2023, "Michael S. Tsirkin" wrote: > On Tue, Mar 21, 2023 at 04:30:57PM +0100, Cornelia Huck wrote: >> On Tue, Mar 21 2023, Viktor Prutyanov wrote: >>=20 >> > On Tue, Mar 21, 2023 at 5:59=E2=80=AFPM Cornelia Huck wrote: >> >> >> >> On Tue, Mar 21 2023, Viktor Prutyanov wrote: >> >> >> >> > 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, PCI and channel I/O transpor= ts. >> >> > >> >> > Signed-off-by: Viktor Prutyanov >> >> > --- >> >> > 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 >> >> > >> >> > drivers/s390/virtio/virtio_ccw.c | 4 +++- >> >> > drivers/virtio/virtio_mmio.c | 14 +++++++++++++- >> >> > drivers/virtio/virtio_pci_common.c | 10 ++++++++++ >> >> > drivers/virtio/virtio_pci_common.h | 4 ++++ >> >> > drivers/virtio/virtio_pci_legacy.c | 2 +- >> >> > drivers/virtio/virtio_pci_modern.c | 2 +- >> >> > drivers/virtio/virtio_ring.c | 17 +++++++++++++++++ >> >> > include/linux/virtio_ring.h | 2 ++ >> >> > include/uapi/linux/virtio_config.h | 6 ++++++ >> >> > 9 files changed, 57 insertions(+), 4 deletions(-) >> >> > >> >> > diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio= /virtio_ccw.c >> >> > index 954fc31b4bc7..c33172c5b8d5 100644 >> >> > --- a/drivers/s390/virtio/virtio_ccw.c >> >> > +++ b/drivers/s390/virtio/virtio_ccw.c >> >> > @@ -396,13 +396,15 @@ static bool virtio_ccw_kvm_notify(struct virt= queue *vq) >> >> > struct virtio_ccw_vq_info *info =3D vq->priv; >> >> > struct virtio_ccw_device *vcdev; >> >> > struct subchannel_id schid; >> >> > + u32 data =3D __virtio_test_bit(vq->vdev, VIRTIO_F_NOTIFICATIO= N_DATA) ? >> >> > + vring_notification_data(vq) : vq->index; >> >> > >> >> > vcdev =3D to_vc_device(info->vq->vdev); >> >> > ccw_device_get_schid(vcdev->cdev, &schid); >> >> > BUILD_BUG_ON(sizeof(struct subchannel_id) !=3D sizeof(unsigne= d int)); >> >> > info->cookie =3D 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; >> >> > diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_m= mio.c >> >> > index 3ff746e3f24a..7c16e622c33d 100644 >> >> > --- a/drivers/virtio/virtio_mmio.c >> >> > +++ b/drivers/virtio/virtio_mmio.c >> >> > @@ -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 =3D to_virtio_mmio_device(v= q->vdev); >> >> > + u32 data =3D vring_notification_data(vq); >> >> > + >> >> > + writel(data, vm_dev->base + VIRTIO_MMIO_QUEUE_NOTIFY); >> >> >> >> Can't you simply use the same method as for ccw, i.e. use one callback >> >> function that simply writes one value or the other? >> > >> > The idea is to eliminate the conditional branch induced by feature bit >> > testing from the notification function. Probably, this can be done in >> > the same way in ccw. >>=20 >> Hm, how noticable is that branch? IOW, is it worth making the code less >> readable for this? > > I'm not sure but these things add up. I'm with Viktor here let's just > avoid the branch and not worry about whether it's important or not. > So let's use the same thing here then? And we can use a subfunction > to avoid code duplication. Ok, let's do it that way. > >> (In any case, all transports probably should use the same method.)