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 87CB5C46CA1 for ; Mon, 18 Sep 2023 05:15:05 +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 D5D0479568 for ; Mon, 18 Sep 2023 05:15:04 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id BADD598641A for ; Mon, 18 Sep 2023 05:15:04 +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 A4469983DFF; Mon, 18 Sep 2023 05:15:04 +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 9008898638E; Mon, 18 Sep 2023 05:15:03 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-IronPort-AV: E=McAfee;i="6600,9927,10836"; a="359821345" X-IronPort-AV: E=Sophos;i="6.02,155,1688454000"; d="scan'208";a="359821345" X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10836"; a="888897711" X-IronPort-AV: E=Sophos;i="6.02,155,1688454000"; d="scan'208";a="888897711" Message-ID: <90ffd64c-9997-3ebb-6d4b-6fdb8d1bdb4f@intel.com> Date: Mon, 18 Sep 2023 13:14:56 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.15.1 Content-Language: en-US To: Parav Pandit , "Michael S. Tsirkin" Cc: "jasowang@redhat.com" , "eperezma@redhat.com" , "cohuck@redhat.com" , "stefanha@redhat.com" , "virtio-comment@lists.oasis-open.org" , "virtio-dev@lists.oasis-open.org" References: <20230906081637.32185-1-lingshan.zhu@intel.com> <20230906081637.32185-3-lingshan.zhu@intel.com> <20230914073023-mutt-send-email-mst@kernel.org> <258989c9-8c5f-c72e-c03d-aabf11f9823d@intel.com> <20230915070504-mutt-send-email-mst@kernel.org> <3ff7e79f-8fbb-4e3e-eb12-17ed8943fe6f@intel.com> From: "Zhu, Lingshan" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH 2/5] virtio: introduce SUSPEND bit in device status On 9/18/2023 12:42 PM, Parav Pandit wrote: >> From: virtio-comment@lists.oasis-open.org > open.org> On Behalf Of Zhu, Lingshan >> Sent: Monday, September 18, 2023 8:27 AM > >> a new feature bit: VIRTIO_F_RING_SUSPEND_RESET. If this feature bit has been >> negotiated then the device allow reset a vq after SUSPEND. > This is simply a wrong semantics to build to operate individual object after its parent object is suspended. A device can choose to respond to a set of signals and ignore others, right? And, This is not your admin vq based LM solution, therefore there is NO PARENT objects. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org