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 5517ECDB483 for ; Thu, 12 Oct 2023 10:23:34 +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 A684E129207 for ; Thu, 12 Oct 2023 10:23:33 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 8F919986838 for ; Thu, 12 Oct 2023 10:23:33 +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 8466B986474; Thu, 12 Oct 2023 10:23:33 +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 7641F98660E for ; Thu, 12 Oct 2023 10:23:33 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-IronPort-AV: E=McAfee;i="6600,9927,10860"; a="471145220" X-IronPort-AV: E=Sophos;i="6.03,218,1694761200"; d="scan'208";a="471145220" X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10860"; a="1001503720" X-IronPort-AV: E=Sophos;i="6.03,218,1694761200"; d="scan'208";a="1001503720" Message-ID: <6f91e124-aac7-cf50-d53c-bebb74faadd3@intel.com> Date: Thu, 12 Oct 2023 18:23:25 +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: "Michael S. Tsirkin" Cc: Parav Pandit , Jason Wang , "virtio-comment@lists.oasis-open.org" , "cohuck@redhat.com" , "sburla@marvell.com" , Shahaf Shuler , Maor Gottlieb , Yishai Hadas References: <20231008112555.473895-1-parav@nvidia.com> <20231008112555.473895-2-parav@nvidia.com> <20231009121638-mutt-send-email-mst@kernel.org> <25375529-9c40-9ea9-692e-f557c514c72f@intel.com> <20231011154930-mutt-send-email-mst@kernel.org> From: "Zhu, Lingshan" In-Reply-To: <20231011154930-mutt-send-email-mst@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [virtio-comment] [PATCH v1 1/8] admin: Add theory of operation for device migration On 10/12/2023 3:51 AM, Michael S. Tsirkin wrote: > On Tue, Oct 10, 2023 at 04:57:52PM +0800, Zhu, Lingshan wrote: >> >> On 10/10/2023 1:21 AM, Parav Pandit wrote: >>>> From: Michael S. Tsirkin >>>> Sent: Monday, October 9, 2023 9:50 PM >>>>>>> One or more passthrough PCI VF devices are ubiquitous for virtual >>>>>>> machines usage using generic kernel framework such as vfio [1]. >>>>>> Mentioning a specific subsystem in a specific OS may mislead the >>>>>> user to think it can only work in that setup. Let's not do that, >>>>>> virtio is not only used for Linux and VFIO. >>>>> This is just one example on how these commands are useful. >>>>> It can be useful in more ways too in more OSes too. >>>>> I will drop from the patch commit log and keep as information purpose in >>>> cover letter. >>>>> Would that work for you? >>>>> >>>>> I don’t have any strong opinion to keep it or remove it as most stakeholders >>>> has the clear view of requirements now. >>>>> Let me know. >>>> So some people use VFs with VFIO. Hence the module name. This sentence by >>>> itself seems to have zero value for the spec. Just drop it. >>> Ok. Will drop. >> So > This is apropos what? Maybe cut off, what is this referring to? > >> why not build your admin vq live migration on our config space solution, >> get out of the troubles, to make your life easier? >> Actually you don't see any technical problems in our config space proposal, >> right? > The status bit one? You enumerated some reasons yourself did you not? > And I sent some right when you asked for help seeing more... or did it go right past? Yes and I have replied in that thread. > > > 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/ > 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/