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 ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AD70CC4167D for ; Fri, 3 Nov 2023 10:35:50 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id E54F07751E for ; Fri, 3 Nov 2023 10:35:38 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id DE012986C3B for ; Fri, 3 Nov 2023 10:35:38 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id D3F92986C2E; Fri, 3 Nov 2023 10:35:38 +0000 (UTC) Mailing-List: contact virtio-comment-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 199A6986C32 for ; Fri, 3 Nov 2023 10:34:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-IronPort-AV: E=McAfee;i="6600,9927,10882"; a="373962307" X-IronPort-AV: E=Sophos;i="6.03,273,1694761200"; d="scan'208";a="373962307" X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10882"; a="738043237" X-IronPort-AV: E=Sophos;i="6.03,273,1694761200"; d="scan'208";a="738043237" From: Zhu Lingshan To: jasowang@redhat.com, mst@redhat.com, eperezma@redhat.com, cohuck@redhat.com, stefanha@redhat.com Cc: virtio-comment@lists.oasis-open.org, parav@nvidia.com, Zhu Lingshan Date: Fri, 3 Nov 2023 18:34:34 +0800 Message-Id: <20231103103437.72784-4-lingshan.zhu@intel.com> X-Mailer: git-send-email 2.35.3 In-Reply-To: <20231103103437.72784-1-lingshan.zhu@intel.com> References: <20231103103437.72784-1-lingshan.zhu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [virtio-comment] [PATCH V2 3/6] virtio: dont reset vqs when SUSPEND When SUSPEND is set, device states and virtqueue states should be stablized, therefore the driver should not reset vqs when SUSPEND is set in device status. Signed-off-by: Zhu Lingshan --- content.tex | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content.tex b/content.tex index bcc9d4b..060b5c2 100644 --- a/content.tex +++ b/content.tex @@ -444,6 +444,9 @@ \subsubsection{Virtqueue Reset}\label{sec:Basic Facilities of a Virtio Device / The device MUST reset any state of a virtqueue to the default state, including the available state and the used state. +If VIRTIO_F_SUSPEND is negotiated and SUSPEND is set in \field{device status}, +the driver SHOULD NOT reset any virtqueues. + \drivernormative{\paragraph}{Virtqueue Reset}{Basic Facilities of a Virtio Device / Virtqueues / Virtqueue Reset / Virtqueue Reset} After the driver tells the device to reset a queue, the driver MUST verify that -- 2.35.3 This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/