Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp27493715rwd; Tue, 4 Jul 2023 03:55:36 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7lpA/aWld9Ep/o+lhj+/Lf+QPZErp0mjBCz2e65pKOKa3nGiVY/q7svYWTlBnC0HEJb6nY X-Received: by 2002:a05:6808:f06:b0:3a3:63f2:eff with SMTP id m6-20020a0568080f0600b003a363f20effmr15465653oiw.4.1688468135864; Tue, 04 Jul 2023 03:55:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688468135; cv=none; d=google.com; s=arc-20160816; b=Ez+dIvS1fodNDFUG1XhPkswmCKgeVcu9ljGBYsbaQYB9OTZYLvSQUh+9Dc0HLCKGWZ e9xrnR5yOqkDSIOtUnHE1+tBGRM1HnHy12f0XS3qlARKFjFZDTGfAZrNpVS1/SkpfnpW BH6y3GcnenZIXxp/iiP03RYssvcWPHSUoxnsxBuEl1oBGb7ATEU/kvP3jBJbwBt0/AF8 Fmo6w/tgA9Kll2KJKMmakcQezG46SSPwJ8PKORFzaiEwKy6DRw0auGm9Gt6mwXzXCBx1 nCqUYV0ffrfGvHPpqI+ccsD7eKLGoHzWvxTXPnLALQ6FbIRpwdcge+J2hKxLhTZqPRiT CH/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=QRorza6OJCiLsVesM2IH/LA8g4F1XVqMOWMx+3P1rz4=; fh=nxJ7nUzbj7fNQ5+IvFr9CwXyzV2FO/3ZGhMHH9rFTqk=; b=tUZtnIUPvUh2La0wzWtred26mz1mPZGeO6i6kPW2C/x4Uo5mv/UfxKH3v4nufPEFio wXn1iZ+CX39uAwPylRsBZESWZLisfMch8+iV0f+0zMOxQKpGTrz8GiuT7gBPcYOJUrkv E+ZrnD4MvfMOUyVtxBaxgKyDnXt4X5Eksq3iASP6KR25xl7Dy5mDW8WfWUf83BXNk39Z Jbm3qHlWY1+B6K3o51GH31Kof4TG7erBaugyITJfKZRXnho4hXku6xNfBuT4QZFjpKkU V/x1D6oj6IJKwUnxTcc6N5ArTjixAijVVt4V50hMFzA0LeKDjo3KTSDkajTTHL0PuFyr izBg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eFUP8Klt; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y30-20020a634b1e000000b00534780446d9si20236873pga.640.2023.07.04.03.55.21; Tue, 04 Jul 2023 03:55: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=@redhat.com header.s=mimecast20190719 header.b=eFUP8Klt; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231639AbjGDKjh (ORCPT + 99 others); Tue, 4 Jul 2023 06:39:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52474 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231433AbjGDKj0 (ORCPT ); Tue, 4 Jul 2023 06:39:26 -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 ESMTPS id 3F034184 for ; Tue, 4 Jul 2023 03:38:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688467122; 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=QRorza6OJCiLsVesM2IH/LA8g4F1XVqMOWMx+3P1rz4=; b=eFUP8KltG+A4OaQ1oLEYkImF+WrLxAAsZp8KbxKYc4gx1Maxop1HEbVZTV61QnpOkNrKhM qP876IhyPgyzav7mqSCJpRoiXmsfKmjoq34hCNei/PM4YhqEVDF6TnD17Q4UOyVVUlgsZb t40geY/H8CuIb20Nm0HhMyQCY6RXb4c= Received: from mail-lf1-f70.google.com (mail-lf1-f70.google.com [209.85.167.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-569-VirDhh_RPDC99n2e51UEgA-1; Tue, 04 Jul 2023 06:38:41 -0400 X-MC-Unique: VirDhh_RPDC99n2e51UEgA-1 Received: by mail-lf1-f70.google.com with SMTP id 2adb3069b0e04-4fb89482c48so4794940e87.3 for ; Tue, 04 Jul 2023 03:38:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688467120; x=1691059120; h=in-reply-to:content-transfer-encoding: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=QRorza6OJCiLsVesM2IH/LA8g4F1XVqMOWMx+3P1rz4=; b=IlcWsYVGPGDX2C7NlcQGznc4Xi4GyYru2VMSgXt39qgsxBFiN26oeTdzhfGbaGwz5B O246pxq6CoqSq5DA40B0AnTIO06jdOnUV+D3yLsErh28i4338KOwrPJJyj4ruiBy1fkw aDcph93DxoMJgaEBEY0MuXqYHgctsO5J5ZtZKM3xMYqjSv+K69VE6IgiaNPcmWdyfFjA T0Q2nEyUyJ06TUZT1XD2l4TvNyQz1+flG3uWErcfD4bDCQ+vCMbz3XaFWGOF0YAwbOCM D4Hpy8JrcUnMi0kCZjXnxroRX5XmwmyEI2MFB5Fg2bR+HlpvNcezGXpZcXo1haktJ6jS Lb6Q== X-Gm-Message-State: ABy/qLZdafWK8Yod2vSFgxYm0mAevFDHl47ZiAsV/X6bcNfHVvrPoFH9 Hp2a9WaShLGIk+bIrQDxh5j8ELDNTy9KnGwPBgXd9wOotevXbC3RXcNpJgdNHZsx5JXqJ+kPMjX mrs8yqjj/k4zKQ/mN007sFFx2 X-Received: by 2002:a05:6512:39d3:b0:4f7:405f:72e7 with SMTP id k19-20020a05651239d300b004f7405f72e7mr10638812lfu.50.1688467119711; Tue, 04 Jul 2023 03:38:39 -0700 (PDT) X-Received: by 2002:a05:6512:39d3:b0:4f7:405f:72e7 with SMTP id k19-20020a05651239d300b004f7405f72e7mr10638796lfu.50.1688467119354; Tue, 04 Jul 2023 03:38:39 -0700 (PDT) Received: from redhat.com ([2.52.13.33]) by smtp.gmail.com with ESMTPSA id z7-20020a05600c220700b003fa999cefc0sm23940722wml.36.2023.07.04.03.38.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Jul 2023 03:38:38 -0700 (PDT) Date: Tue, 4 Jul 2023 06:38:35 -0400 From: "Michael S. Tsirkin" To: Eugenio Perez Martin Cc: Jason Wang , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Shannon Nelson , virtualization@lists.linux-foundation.org, kvm@vger.kernel.org Subject: Re: [PATCH] vdpa: reject F_ENABLE_AFTER_DRIVER_OK if backend does not support it Message-ID: <20230704063646-mutt-send-email-mst@kernel.org> References: <20230703142218.362549-1-eperezma@redhat.com> <20230703105022-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham 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 On Tue, Jul 04, 2023 at 12:25:32PM +0200, Eugenio Perez Martin wrote: > On Mon, Jul 3, 2023 at 4:52 PM Michael S. Tsirkin wrote: > > > > On Mon, Jul 03, 2023 at 04:22:18PM +0200, Eugenio Pérez wrote: > > > With the current code it is accepted as long as userland send it. > > > > > > Although userland should not set a feature flag that has not been > > > offered to it with VHOST_GET_BACKEND_FEATURES, the current code will not > > > complain for it. > > > > > > Since there is no specific reason for any parent to reject that backend > > > feature bit when it has been proposed, let's control it at vdpa frontend > > > level. Future patches may move this control to the parent driver. > > > > > > Fixes: 967800d2d52e ("vdpa: accept VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK backend feature") > > > Signed-off-by: Eugenio Pérez > > > > Please do send v3. And again, I don't want to send "after driver ok" hack > > upstream at all, I merged it in next just to give it some testing. > > We want RING_ACCESS_AFTER_KICK or some such. > > > > Current devices do not support that semantic. Which devices specifically access the ring after DRIVER_OK but before a kick? > My plan was to convert > it in vp_vdpa if needed, and reuse the current vdpa ops. Sorry if I > was not explicit enough. > > The only solution I can see to that is to trap & emulate in the vdpa > (parent?) driver, as talked in virtio-comment. But that complicates > the architecture: > * Offer VHOST_BACKEND_F_RING_ACCESS_AFTER_KICK > * Store vq enable state separately, at > vdpa->config->set_vq_ready(true), but not transmit that enable to hw > * Store the doorbell state separately, but do not configure it to the > device directly. > > But how to recover if the device cannot configure them at kick time, > for example? > > Maybe we can just fail if the parent driver does not support enabling > the vq after DRIVER_OK? That way no new feature flag is needed. > > Thanks! > > > > > > --- > > > Sent with Fixes: tag pointing to git.kernel.org/pub/scm/linux/kernel/git/mst > > > commit. Please let me know if I should send a v3 of [1] instead. > > > > > > [1] https://lore.kernel.org/lkml/20230609121244-mutt-send-email-mst@kernel.org/T/ > > > --- > > > drivers/vhost/vdpa.c | 7 +++++-- > > > 1 file changed, 5 insertions(+), 2 deletions(-) > > > > > > diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c > > > index e1abf29fed5b..a7e554352351 100644 > > > --- a/drivers/vhost/vdpa.c > > > +++ b/drivers/vhost/vdpa.c > > > @@ -681,18 +681,21 @@ static long vhost_vdpa_unlocked_ioctl(struct file *filep, > > > { > > > struct vhost_vdpa *v = filep->private_data; > > > struct vhost_dev *d = &v->vdev; > > > + const struct vdpa_config_ops *ops = v->vdpa->config; > > > void __user *argp = (void __user *)arg; > > > u64 __user *featurep = argp; > > > - u64 features; > > > + u64 features, parent_features = 0; > > > long r = 0; > > > > > > if (cmd == VHOST_SET_BACKEND_FEATURES) { > > > if (copy_from_user(&features, featurep, sizeof(features))) > > > return -EFAULT; > > > + if (ops->get_backend_features) > > > + parent_features = ops->get_backend_features(v->vdpa); > > > if (features & ~(VHOST_VDPA_BACKEND_FEATURES | > > > BIT_ULL(VHOST_BACKEND_F_SUSPEND) | > > > BIT_ULL(VHOST_BACKEND_F_RESUME) | > > > - BIT_ULL(VHOST_BACKEND_F_ENABLE_AFTER_DRIVER_OK))) > > > + parent_features)) > > > return -EOPNOTSUPP; > > > if ((features & BIT_ULL(VHOST_BACKEND_F_SUSPEND)) && > > > !vhost_vdpa_can_suspend(v)) > > > -- > > > 2.39.3 > >