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 C5D20EB8FA5 for ; Wed, 6 Sep 2023 08:17:36 +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 A487268485 for ; Wed, 6 Sep 2023 08:17:21 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 973BC9865D1 for ; Wed, 6 Sep 2023 08:17:21 +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 880999865C9; Wed, 6 Sep 2023 08:17:21 +0000 (UTC) Mailing-List: contact virtio-dev-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 75A5A986605; Wed, 6 Sep 2023 08:17:17 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-IronPort-AV: E=McAfee;i="6600,9927,10824"; a="374397940" X-IronPort-AV: E=Sophos;i="6.02,231,1688454000"; d="scan'208";a="374397940" X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10824"; a="741439941" X-IronPort-AV: E=Sophos;i="6.02,231,1688454000"; d="scan'208";a="741439941" 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, virtio-dev@lists.oasis-open.org, Zhu Lingshan Date: Wed, 6 Sep 2023 16:16:36 +0800 Message-Id: <20230906081637.32185-5-lingshan.zhu@intel.com> X-Mailer: git-send-email 2.35.3 In-Reply-To: <20230906081637.32185-1-lingshan.zhu@intel.com> References: <20230906081637.32185-1-lingshan.zhu@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [virtio-dev] [PATCH 4/5] virtqueue: ignore resetting vqs when SUSPEND When SUSPEND is set, the device should stabilize the device states and virtqueue states, therefore the device should ignore resetting 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 9d727ce..cd2b426 100644 --- a/content.tex +++ b/content.tex @@ -443,6 +443,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 device SHOULD ignore resetting 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 --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org