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 CD693C61D97 for ; Fri, 24 Nov 2023 12:10:29 +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 1FF262AEE0 for ; Fri, 24 Nov 2023 12:10:29 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id DEAC09868B5 for ; Fri, 24 Nov 2023 12:10:28 +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 BFA829862D9; Fri, 24 Nov 2023 12:10:28 +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 AFFAE9868A5 for ; Fri, 24 Nov 2023 12:10:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: BnNY5F8kM_SaVxMGo20bmQ-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700827825; x=1701432625; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wOcfKcLKURGy5rvsZ0J7b+OiNMUwIHGDNzQLcC1rPxU=; b=TI1qyrRu1VmLROmfeuo40IaodEzmZNUAXYHXgC8p1wVYzUCLkzGVW+4OO23w3PJ0vy CK8iqrIibcVB/jur2vlA0kkLnictAEdVknHPB20JcMvbEVOAHKaCkN3uwbpYHC/x8ZRK bt9fRjLHsTK3m3e9YM3+TXextBOEaOEY+EkaOIc/CWAxUwHSnqAezmBi7WLgFsXHxXT/ 2O04nEzd4QP/H5QLssGmy78i3XBpIlimRikhul6aWzWR2tMu9X/O78aJpnxwc1ImdbaO hVKYHpC2Mh4ot5uf2bLVEaHGTI+SU8u2ZOixTiQyi2CrirpYOGHIXzpRB7hpWc0jidgx TLpw== X-Gm-Message-State: AOJu0YxavAuWl0CTFdCcKf6cRCFx57mbYqJ977XIJFn8trxYDE5B1HqD ppKIMzfUONq1kApc7+bvWiDA0WVsHT3AhvwmCY/nwhMklyxP0EOSoda0h8yjRHDdFBOndpxCjMU svzkKkguQRlVQ2KMYOZ5oU0KKYzU36idNYg== X-Received: by 2002:a17:907:1c99:b0:a01:977a:ed73 with SMTP id nb25-20020a1709071c9900b00a01977aed73mr2213556ejc.8.1700827825366; Fri, 24 Nov 2023 04:10:25 -0800 (PST) X-Google-Smtp-Source: AGHT+IGoDj14L+k9rXdO+XfxyNJ4ZM6OuqKj1dlXw1PTL4yBmZpjanfALVaUr7YTAJdwAdtuYXFoLg== X-Received: by 2002:a17:907:1c99:b0:a01:977a:ed73 with SMTP id nb25-20020a1709071c9900b00a01977aed73mr2213525ejc.8.1700827824954; Fri, 24 Nov 2023 04:10:24 -0800 (PST) Date: Fri, 24 Nov 2023 07:10:20 -0500 From: "Michael S. Tsirkin" To: Jason Wang Cc: Parav Pandit , "Zhu, Lingshan" , "virtio-comment@lists.oasis-open.org" , "cohuck@redhat.com" , "sburla@marvell.com" , Shahaf Shuler , Maor Gottlieb , Yishai Hadas Message-ID: <20231124070519-mutt-send-email-mst@kernel.org> References: <20231117063406-mutt-send-email-mst@kernel.org> <20231124063537-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: Re: [virtio-comment] [PATCH v1 1/8] admin: Add theory of operation for device migration On Fri, Nov 24, 2023 at 07:51:06PM +0800, Jason Wang wrote: > On Fri, Nov 24, 2023 at 7:38 PM Michael S. Tsirkin wrote: > > > > On Fri, Nov 24, 2023 at 11:07:53AM +0800, Jason Wang wrote: > > > How TDISP/attestation is related to a specific device driver? How can > > > a legacy DPDK driver break things like attestation here? > > > > > > > Hence it is not applicable. > > > > > > Wow. The legacy tunnel was just invented by you for just several > > > months and soon became a second-class citizen in the proposal here? > > > > Legacy is not going to be a 1st class citizen and that was a > > concious decision the TC made. > > In particular we know straight > > away that there is no way to make them safely work > > while preserving assumptions confidential computing > > guests make (which I guess is what you mean here). > > Probably, but I think we need to support its migration without TD. Ah, migration of legacy guests is an interesting point. Bringing up TD was just confusing. I expect this to be rather painless to add precisely because this proposal does not reply on either modern or legacy pci layout. But details need to be thought through, I agree. I don't see why this is not applicable - definitely people are used to be able to migrate these guests. > > The whole point of isolating legacy mess in the special > > commands was so we don't try to support them going forward, > > don't try to add new features for legacy interfaces please. > > Thanks > > > > > > -- > > MST > > 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/