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 9DBD0CCA473 for ; Mon, 27 Jun 2022 11:58:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237839AbiF0L66 (ORCPT ); Mon, 27 Jun 2022 07:58:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239522AbiF0L5s (ORCPT ); Mon, 27 Jun 2022 07:57:48 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id AE405BCB6 for ; Mon, 27 Jun 2022 04:53:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1656330812; 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=R4iA+zJThegEvaay5X9bkB6r2mlx5a4ueL2JEW4gqMI=; b=TA+uUJSSAXxi439YnvjU0idz0Fh9Rjk6i2w+2sga1ZNo44Hd5nmyltefb0YtS5GrUCh9Jk V7fmNPGR0F96m9eq4JU9b3Bq9hDuVpOakgWqZq7Mbt8eCsnSrZxoTRbMI+fx+gGI56lZ0S dzCdXBMY2+R+gbAi8elMRlAB306dAvQ= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-395-qMw_IohCNeeo44pECcX82A-1; Mon, 27 Jun 2022 07:53:31 -0400 X-MC-Unique: qMw_IohCNeeo44pECcX82A-1 Received: by mail-wr1-f70.google.com with SMTP id n7-20020adfc607000000b0021a37d8f93aso1140038wrg.21 for ; Mon, 27 Jun 2022 04:53:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=R4iA+zJThegEvaay5X9bkB6r2mlx5a4ueL2JEW4gqMI=; b=Ei+hVhJdlli4OGzsbzKOcf/jZrhATfBRnDLT3cqdufJSyM5MpWQ43QJ+zBQzvjLO0U nWlifeo+TC0modChfGFJsf10E5Hwhf4w29zjJO7yj4UzvIQ4tEjAjLLnwLmpvkQt4SUN qaE43sidThPJVgZLSWMt6bltoO7C1EW1XfzWhDwLF1q3IMF2cgCMPwAUKxGc13q22klo hsrNB87eiScqECfznQexa9/MFvWTX10CfsZjuNTr8vDZZ2Zg9IoS77+E9n/JsaaPQxuT D41p0HtmhW2F/nDxvey0HPbBNLvZJU4zwRkMtLC2LCdNwa4FKGgc4iDX8L4CS1//6ZUD igxQ== X-Gm-Message-State: AJIora9jd5U36AkLzcKiIVCDbQ69smdD306rm5jbCOE8sb+H4s2a3+vX ndUmDO5IHxfwh8AjMd/PHpDtVLos1phWShaGdotktwNnfG+KCOG4vnL2NLn/KeuQDF5+MlI2tnF UCIVJT4NxnNmijhgliFaFHw== X-Received: by 2002:a1c:7c18:0:b0:3a0:39b1:3403 with SMTP id x24-20020a1c7c18000000b003a039b13403mr21172922wmc.84.1656330810176; Mon, 27 Jun 2022 04:53:30 -0700 (PDT) X-Google-Smtp-Source: AGRyM1umV07YHfv9l89u85pmjMFPA0YWmqYXm7VuXyf0J+ISW9dEoHO5P2MBiXRfYI/0CpLN0ZOgWg== X-Received: by 2002:a1c:7c18:0:b0:3a0:39b1:3403 with SMTP id x24-20020a1c7c18000000b003a039b13403mr21172868wmc.84.1656330809951; Mon, 27 Jun 2022 04:53:29 -0700 (PDT) Received: from redhat.com ([2.54.45.90]) by smtp.gmail.com with ESMTPSA id a19-20020a05600c349300b0039db500714fsm13454861wmq.6.2022.06.27.04.53.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 27 Jun 2022 04:53:29 -0700 (PDT) Date: Mon, 27 Jun 2022 07:53:22 -0400 From: "Michael S. Tsirkin" To: Jason Wang Cc: Xuan Zhuo , virtualization , Richard Weinberger , Anton Ivanov , Johannes Berg , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Hans de Goede , Mark Gross , Vadim Pasternak , Bjorn Andersson , Mathieu Poirier , Cornelia Huck , Halil Pasic , Eric Farman , Heiko Carstens , Vasily Gorbik , Alexander Gordeev , Christian Borntraeger , Sven Schnelle , Alexei Starovoitov , Daniel Borkmann , Jesper Dangaard Brouer , John Fastabend , Vincent Whitchurch , linux-um@lists.infradead.org, netdev , platform-driver-x86@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-s390@vger.kernel.org, kvm , "open list:XDP (eXpress Data Path)" , kangjie.xu@linux.alibaba.com Subject: Re: [PATCH v10 25/41] virtio_pci: struct virtio_pci_common_cfg add queue_notify_data Message-ID: <20220627074723-mutt-send-email-mst@kernel.org> References: <20220624025621.128843-1-xuanzhuo@linux.alibaba.com> <20220624025621.128843-26-xuanzhuo@linux.alibaba.com> <20220624025817-mutt-send-email-mst@kernel.org> <20220627023841-mutt-send-email-mst@kernel.org> <20220627034733-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-s390@vger.kernel.org On Mon, Jun 27, 2022 at 04:14:20PM +0800, Jason Wang wrote: > On Mon, Jun 27, 2022 at 3:58 PM Michael S. Tsirkin wrote: > > > > On Mon, Jun 27, 2022 at 03:45:30PM +0800, Jason Wang wrote: > > > On Mon, Jun 27, 2022 at 2:39 PM Michael S. Tsirkin wrote: > > > > > > > > On Mon, Jun 27, 2022 at 10:30:42AM +0800, Jason Wang wrote: > > > > > On Fri, Jun 24, 2022 at 2:59 PM Michael S. Tsirkin wrote: > > > > > > > > > > > > On Fri, Jun 24, 2022 at 10:56:05AM +0800, Xuan Zhuo wrote: > > > > > > > Add queue_notify_data in struct virtio_pci_common_cfg, which comes from > > > > > > > here https://github.com/oasis-tcs/virtio-spec/issues/89 > > > > > > > > > > > > > > For not breaks uABI, add a new struct virtio_pci_common_cfg_notify. > > > > > > > > > > > > What exactly is meant by not breaking uABI? > > > > > > Users are supposed to be prepared for struct size to change ... no? > > > > > > > > > > Not sure, any doc for this? > > > > > > > > > > Thanks > > > > > > > > > > > > Well we have this: > > > > > > > > The drivers SHOULD only map part of configuration structure > > > > large enough for device operation. The drivers MUST handle > > > > an unexpectedly large \field{length}, but MAY check that \field{length} > > > > is large enough for device operation. > > > > > > Yes, but that's the device/driver interface. What's done here is the > > > userspace/kernel. > > > > > > Userspace may break if it uses e.g sizeof(struct virtio_pci_common_cfg)? > > > > > > Thanks > > > > Hmm I guess there's risk... but then how are we going to maintain this > > going forward? Add a new struct on any change? > > This is the way we have used it for the past 5 or more years. I don't > see why this must be handled in the vq reset feature. > > >Can we at least > > prevent this going forward somehow? > > Like have some padding? > > Thanks Maybe - this is what QEMU does ... > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Since I want to add queue_reset after queue_notify_data, I submitted > > > > > > > this patch first. > > > > > > > > > > > > > > Signed-off-by: Xuan Zhuo > > > > > > > Acked-by: Jason Wang > > > > > > > --- > > > > > > > include/uapi/linux/virtio_pci.h | 7 +++++++ > > > > > > > 1 file changed, 7 insertions(+) > > > > > > > > > > > > > > diff --git a/include/uapi/linux/virtio_pci.h b/include/uapi/linux/virtio_pci.h > > > > > > > index 3a86f36d7e3d..22bec9bd0dfc 100644 > > > > > > > --- a/include/uapi/linux/virtio_pci.h > > > > > > > +++ b/include/uapi/linux/virtio_pci.h > > > > > > > @@ -166,6 +166,13 @@ struct virtio_pci_common_cfg { > > > > > > > __le32 queue_used_hi; /* read-write */ > > > > > > > }; > > > > > > > > > > > > > > +struct virtio_pci_common_cfg_notify { > > > > > > > + struct virtio_pci_common_cfg cfg; > > > > > > > + > > > > > > > + __le16 queue_notify_data; /* read-write */ > > > > > > > + __le16 padding; > > > > > > > +}; > > > > > > > + > > > > > > > /* Fields in VIRTIO_PCI_CAP_PCI_CFG: */ > > > > > > > struct virtio_pci_cfg_cap { > > > > > > > struct virtio_pci_cap cap; > > > > > > > -- > > > > > > > 2.31.0 > > > > > > > > > > > >