From nobody Fri May 17 10:13:23 2024 Delivered-To: importer@patchew.org Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org ARC-Seal: i=1; a=rsa-sha256; t=1597313020; cv=none; d=zohomail.com; s=zohoarc; b=EfSogqMac2bcjqY2PcqjQahl6jFy3tK5mi+aG2zKCqVFTEG373wSyURGPhY9/ri+WP6fCgvmcivxfibFh06z6IxgvFikb2wgA/9KBarNU/bjc23lKLpMKstuEwKg09Ox3RC7ZHEh+5zhhTyAk1M+4PoGRW0OaEIeOEoL7/T/U+I= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1597313020; h=Content-Transfer-Encoding:Cc:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=FEEaNLmB6GOe5gfKhgL3ys6g6/aCgwfXoso39Kjy2R8=; b=Cy1GC1K66ip6fdzNxGf+VmUrhbQOrWC3ouD8wt0MjBd3IyTSfLelKorwHy3Jh7AdZycWVY+/heQA+iI/IelS7jPXsm406MuNfA862YGvQMtrU8xFDKjkpm/Ite4Vzy4lWNtaEVBFT0ceMVcdLcCq82x+J8dgnrVoqvFWVaYhUSU= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org Return-Path: Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) by mx.zohomail.com with SMTPS id 1597313019609594.1535489574835; Thu, 13 Aug 2020 03:03:39 -0700 (PDT) Received: from localhost ([::1]:45248 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k6A5B-0001BR-IY for importer@patchew.org; Thu, 13 Aug 2020 06:03:37 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:43682) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k6A3C-0000F4-Nv for qemu-devel@nongnu.org; Thu, 13 Aug 2020 06:01:34 -0400 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]:58055) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k6A39-00038X-V2 for qemu-devel@nongnu.org; Thu, 13 Aug 2020 06:01:34 -0400 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 390EC999; Thu, 13 Aug 2020 05:49:34 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 13 Aug 2020 05:49:34 -0400 Received: from x220.qyliss.net (p54b8e5f4.dip0.t-ipconnect.de [84.184.229.244]) by mail.messagingengine.com (Postfix) with ESMTPA id B4DD93280059; Thu, 13 Aug 2020 05:49:32 -0400 (EDT) Received: by x220.qyliss.net (Postfix, from userid 1000) id 98D741E1; Thu, 13 Aug 2020 09:49:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; s=fm3; bh=FEEaNLmB6GOe5gfKhgL3ys6g6/ aCgwfXoso39Kjy2R8=; b=je7m1KPkqmRgB+AZaN8pXbKSpff1L5UkRyn7+TJIwe lqpWZDXfO2L1v5wy90rwvc7ZzO+2pb0Bxq+2DyCjmtHhb2Niy5RaYcttQmjPTx8d GU4bxId5ds8VhmErMkhsu9Tg65LUhL5xDitWlWyW6+2KTp9bGIZx+7gpH+X06zIW WWDwv33Aj74Gk4BEHWV2g+m3fkN8xngLN/YVSuhX7Ocvdpad5F5cP4iwT4ZVQ895 3CaWsPV5HIkzbkuYEfJJYlm+g6/suhXMpJEuSM96nwQGP0RptZqy68ReBGSl2RLx dFZQ6oi2wSNnymDUWuWKtzQ8TDmlD748Q7ryoiTnVCiw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:date:from :message-id:mime-version:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=FEEaNLmB6GOe5gfKh gL3ys6g6/aCgwfXoso39Kjy2R8=; b=HplBOSZea1VyKCVSZSbTCGgjSSNAPCqXs qEMdjnimBhjQFrXbfOmLF8tk/Xty6Lv5ukwO/tMJ+wLC2EKDZnzF6sU8akx3codA kYZZftWzgV+DzpwMc4KfqaoODM0Ep3UtYRsrf525nllBpCwzv+hXME4aSpVUdfDj co4gZrbhMnub+2u5syBkkhOKEz04CVkKwJw7nrKfxASJtOnuHEpItxtSzJtNGm2o 3Ifjll9tVielLkeuSV11ZiSZLL2F3vVe/F59ajZm+jVwm3CUZqClpoykIAxuU1hI tJY5/m+LKvmcdGJOV3e+krikKhPBXqQ2obcm5cKDTOyGF24ugR8rg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrleeggddvvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkffoggfgsedtkeertdertd dtnecuhfhrohhmpeetlhihshhsrgcutfhoshhsuceohhhisegrlhihshhsrgdrihhsqeen ucggtffrrghtthgvrhhnpeehgfdtleeiffeuveegkeeuffehvdevhfetfeehfeffleette dvvdegkeduudeggfenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecukfhppeekgedr udekgedrvddvledrvdeggeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpehqhihlihhsshesgidvvddtrdhqhihlihhsshdrnhgvth X-ME-Proxy: From: Alyssa Ross To: qemu-devel@nongnu.org Subject: [PATCH] docs: clarify absence of set_features in vhost-user Date: Thu, 13 Aug 2020 09:48:48 +0000 Message-Id: <20200813094847.4288-1-hi@alyssa.is> X-Mailer: git-send-email 2.27.0 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Received-SPF: pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Received-SPF: softfail client-ip=64.147.123.19; envelope-from=qyliss@x220.qyliss.net; helo=wout3-smtp.messagingengine.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/13 05:51:55 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Michael S . Tsirkin" Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" X-ZohoMail-DKIM: pass (identity @alyssa.is) Content-Type: text/plain; charset="utf-8" The previous wording was (at least to me) ambiguous about whether a backend should enable features immediately after they were set using VHOST_USER_SET_PROTOCOL_FEATURES, or wait for support for protocol features to be acknowledged if it hasn't been yet before enabling those features. This patch attempts to make it clearer that VHOST_USER_SET_PROTOCOL_FEATURES should immediately enable features, even if support for protocol features has not yet been acknowledged, while still also making clear that the frontend SHOULD acknowledge support for protocol features. Previous discussion begins here: Cc: Michael S. Tsirkin Signed-off-by: Alyssa Ross --- docs/interop/vhost-user.rst | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/docs/interop/vhost-user.rst b/docs/interop/vhost-user.rst index 10e3e3475e..bc78c9947f 100644 --- a/docs/interop/vhost-user.rst +++ b/docs/interop/vhost-user.rst @@ -854,9 +854,9 @@ Master message types ``VHOST_USER_GET_FEATURES``. =20 .. Note:: - Slave that reported ``VHOST_USER_F_PROTOCOL_FEATURES`` must - support this message even before ``VHOST_USER_SET_FEATURES`` was - called. + While QEMU should acknowledge ``VHOST_USER_F_PROTOCOL_FEATURES``, a + backend must allow ``VHOST_USER_GET_PROTOCOL_FEATURES`` even if + ``VHOST_USER_F_PROTOCOL_FEATURES`` has not been acknowledged yet. =20 ``VHOST_USER_SET_PROTOCOL_FEATURES`` :id: 16 @@ -869,8 +869,12 @@ Master message types ``VHOST_USER_GET_FEATURES``. =20 .. Note:: - Slave that reported ``VHOST_USER_F_PROTOCOL_FEATURES`` must support - this message even before ``VHOST_USER_SET_FEATURES`` was called. + While QEMU should acknowledge ``VHOST_USER_F_PROTOCOL_FEATURES``, a + backend must allow ``VHOST_USER_SET_PROTOCOL_FEATURES`` even if + ``VHOST_USER_F_PROTOCOL_FEATURES`` has not been acknowledged yet. + The backend must not wait for ``VHOST_USER_SET_FEATURES`` before + enabling protocol features requested with + ``VHOST_USER_SET_PROTOCOL_FEATURES``. =20 ``VHOST_USER_SET_OWNER`` :id: 3 --=20 2.27.0