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 7DDCEE95A91 for ; Mon, 9 Oct 2023 10:06: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 CDD837C3F6 for ; Mon, 9 Oct 2023 10:06: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 C34AA98654B for ; Mon, 9 Oct 2023 10:06: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 B5E2F9864CE; Mon, 9 Oct 2023 10:06: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 A647F9864D3; Mon, 9 Oct 2023 10:06:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-IronPort-AV: E=McAfee;i="6600,9927,10857"; a="381373172" X-IronPort-AV: E=Sophos;i="6.03,210,1694761200"; d="scan'208";a="381373172" X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10857"; a="818804039" X-IronPort-AV: E=Sophos;i="6.03,210,1694761200"; d="scan'208";a="818804039" Message-ID: <3539f99f-2770-428f-2b44-b7ac5a1a0407@intel.com> Date: Mon, 9 Oct 2023 18:05:52 +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" , Cornelia Huck Cc: Jason Wang , "eperezma@redhat.com" , Stefan Hajnoczi , "virtio-comment@lists.oasis-open.org" , "virtio-dev@lists.oasis-open.org" References: <20230926064201-mutt-send-email-mst@kernel.org> <305d9907-9668-d362-1ff2-49a5e9f90e42@intel.com> From: "Zhu, Lingshan" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [virtio-dev] Re: [PATCH 0/5] virtio: introduce SUSPEND bit and vq state On 9/27/2023 6:39 PM, Parav Pandit wrote: > >> From: Zhu, Lingshan >> Sent: Wednesday, September 27, 2023 1:50 PM >> I see his proposal can: >> 1) meet some customers requirements without nested and bare-metal >> 2) align with Nvidia production > Slightly inaccurate. > The work produced is for the virtio spec update for the users. > > I have missed adding other contributors Sign-off who also share similar use cases, which I will add in v1. > >> 3) easier to emulate by onboard SOC >> >> The general purpose of his proposal and mine are aligned: migrate virtio >> devices. >> > Great. > >> Jason has ever proposed to collaborate, please allow me quote his proposal: >> >> " >> Let me repeat once again here for the possible steps to collaboration: >> >> 1) define virtqueue state, inflight descriptors in the section of >> basic facility but not under the admin commands >> 2) define the dirty page tracking, device context/states in the >> section of basic facility but not under the admin commands >> 3) define transport specific interfaces or admin commands to access them >> " >> >> I totally agree with his proposal. > We started discussing some of the it. > If I draw parallels, one should not say "detach descriptors from virtqueue" for the infrastructure that exists in the basic facilities. > If so, one should explain the technical design reason and it would make sense. not sure what is  "detach descriptors from virtqueue", but admin vq carries commands anyway. > > So let's discuss it. > I like to better understand the _real_ technical reason for detaching it. so please to or cc me in your series. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org