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 4AF97C6FD1D for ; Fri, 7 Apr 2023 11:13:23 +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 690082B125 for ; Fri, 7 Apr 2023 11:13:22 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 52F619865D9 for ; Fri, 7 Apr 2023 11:13:22 +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 3FBA99865D7; Fri, 7 Apr 2023 11:13:22 +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 2E1009865D8 for ; Fri, 7 Apr 2023 11:13:22 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: PTZ3STIkPgSkn1HLyrzTzQ-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680865999; 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=x3LFma+lRqmDSh9PxnvYBSCbMmX2XoqjUoTkkwwT28A=; b=qGkPwCnGW5Z/AKstz4ZQ3sMfVeMYELRbeXoADLlvrsorYCq0m3Dun1OKvBXsjZZcva cT73dp5F8p0x7oEo4qAEbafnaSNN4+fhE8hKG+Vw/2oXtLpyaljebVke5AtqyFo8XfUi 9ih8y6vGeVCqN+fh6s2SiSjylcuEO8be/96ppoXXrr81Ek7K70rH4QV0IhrQY4Rhg8i4 FIkCuhFRsuFlosiagoZ1lcYC591oGlUWGEBkoRrOKBh8J+IVrpB6bo8sfe1RUEC4kahW HFaqMbQSXWMg3vrqkK//HojYclQim24hbZQrI3TdLI64HV4BMX/kF3j5oSQGL4fSmiFM G7oQ== X-Gm-Message-State: AAQBX9fCDFXyfiiMFsF2V6DWDGOUN0rbGX++PQRSr05MshdPOLiei+Pu kMFlUSm7Qv5sPEzKJeEbbD7KyLF+GzVX0fRd1meMcyckSZUe5oNwtEfyT6oLxaZca/W2VfoDAmY S+05UP7DS9INU0bOBKjXEUvNLS8YV1U56Cw== X-Received: by 2002:adf:df0b:0:b0:2ef:b139:5973 with SMTP id y11-20020adfdf0b000000b002efb1395973mr1048905wrl.17.1680865998880; Fri, 07 Apr 2023 04:13:18 -0700 (PDT) X-Google-Smtp-Source: AKy350Y1D5XyEBhaTjnWjn8ODLM2+ZhEW/9dJ/g2z84v/8imAJMUaNOuYt1mzrzwBQ0htzHvpcsSqw== X-Received: by 2002:adf:df0b:0:b0:2ef:b139:5973 with SMTP id y11-20020adfdf0b000000b002efb1395973mr1048887wrl.17.1680865998594; Fri, 07 Apr 2023 04:13:18 -0700 (PDT) Date: Fri, 7 Apr 2023 07:13:13 -0400 From: "Michael S. Tsirkin" To: Xuan Zhuo Cc: Wen Gu , Halil Pasic , virtio-comment@lists.oasis-open.org, hans@linux.alibaba.com, herongguang@linux.alibaba.com, zmlcc@linux.alibaba.com, dust.li@linux.alibaba.com, tonylu@linux.alibaba.com, zhenzao@linux.alibaba.com, helinguo@linux.alibaba.com, gerry@linux.alibaba.com, cohuck@redhat.com, jasowang@redhat.com, Jan Kiszka , kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com, hca@linux.ibm.com, twinkler@linux.ibm.com, raspl@linux.ibm.com, virtio-dev@lists.oasis-open.org, Alexandra Winter Message-ID: <20230407070820-mutt-send-email-mst@kernel.org> References: <20230209033056.96657-1-xuanzhuo@linux.alibaba.com> <20230209033056.96657-2-xuanzhuo@linux.alibaba.com> <20230323154656.7f036d52.pasic@linux.ibm.com> <7a9ebec0-5e87-b80f-4f2c-c4db7ae4fe84@linux.ibm.com> <20230405084632-mutt-send-email-mst@kernel.org> <1680837735.392044-2-xuanzhuo@linux.alibaba.com> MIME-Version: 1.0 In-Reply-To: <1680837735.392044-2-xuanzhuo@linux.alibaba.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: Re: [virtio-comment] Re: [virtio-dev] Re: [virtio-comment] [PATCH v3 1/1] virtio-ism: introduce new device virtio-ism On Fri, Apr 07, 2023 at 11:22:15AM +0800, Xuan Zhuo wrote: > On Wed, 5 Apr 2023 08:52:14 -0400, "Michael S. Tsirkin" wrote: > > On Wed, Apr 05, 2023 at 02:39:53PM +0200, Alexandra Winter wrote: > > > > > > > > > On 24.03.23 05:03, Wen Gu wrote: > > > > > > > > > > > > On 2023/3/23 22:46, Halil Pasic wrote: > > > > > > > >> On Thu,  9 Feb 2023 11:30:56 +0800 > > > >> Xuan Zhuo wrote: > > > >> > > > > > > ... > > > > > > > > > > >> To get back to the things proposed here: the cdid is IMHO > > > >> a nice thing, and is functionally corresponding to the > > > >> (S)EID. But it is 16 byte wide, and I have no idea how > > > >> is it supposed to be used in the CLC handshake. > > > >> > > > > > > > > CLC handshake carry one SEID for all the SMC-D device. Considering > > > > coexistence with ISM, I am not sure whether we can change or increase > > > > the SEID.. cc Alexandra > > > > > > > > Thanks! > > > > Wen Gu > > > > > > As mentioned by others, discussions are ongoing. > > > It would be great, if we can agree on a way to use the existing CLC handshake > > > for SMC-D via virtio-ism and ism-loopback. > > > In that case SEID needs to be unique per hardware instance, cannot be increased and > > > can only be changed for x86 in a non-colliding way. > > > > > > An alternative would be to define new a SMC-D(?) protocol variant/version, where we > > > are free to define new fields (e.g. UUIDs). > > > > > > Alexandra > > > > Problem with tying to hardware is that it is blocking > > migration (which is a challenge with ism anyway, but still). > > > We don't want to support migration. At least we don't want to support it for the > time being. Because there are indeed many problems. I think Migration is not > necessary for a new Virtio device. > > Thanks. The specific implementation does not matter much. At the spec level we strive to make interfaces generic so they can be reused down the road, rather than having to invent new ones for each use-case. Maybe we can come up with a way that let devices choose either an existing one with a SEID or a new one with a UUID? -- 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/ 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 BF0E2C76196 for ; Fri, 7 Apr 2023 11:13:24 +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 1D44B3358D for ; Fri, 7 Apr 2023 11:13:24 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 104159865EC for ; Fri, 7 Apr 2023 11:13:24 +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 05ED39865D9; Fri, 7 Apr 2023 11:13:24 +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 E7C8E9865D8 for ; Fri, 7 Apr 2023 11:13:23 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: gECfLG1MPVu6GIUXRhGfdQ-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680865999; 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=x3LFma+lRqmDSh9PxnvYBSCbMmX2XoqjUoTkkwwT28A=; b=keGD64MYHKwPisHJ6BWRCrE8ASdoH8BaRZud+ApFolpzu3yjYenMJP0WjQXS5+PurB njidZfsWJy5yfMi8SlAyuLUUro6xzgX0/mzwqQxTvpKX5wzwrau4tULasgeu53jUTKbS mjCGBnpcuqc70Pbjoltu1ygah6Lg7w/gZqm1k+qZHdYdqJPQUuYJu14URNB3byF4o2od dooxawe+Oq/6VNmru+iQs+NtRM/+XA197hMfbJCiheoWPvoCbOzXB18OlDfLg+3AqCw2 edHDHzkxBD5Mt5Y/2MthCijv+AtsgiVqNpf6CE4pQlco38Vnaco5hq+W6gHaohbJHf2/ Ib1w== X-Gm-Message-State: AAQBX9d1gA/niO9LzD93VpcHystoMju9F/pBkCWlyb6eY1YtdhR7GUJ8 7a1YaGcjTjJk4A7LB1w2q2ISE4NMHBfq6TRkZfMVcflVb4Bzp2TTYls2TW/bF6SvhYr/UYdFzhs B78EIDRwJki+wqkUr6HTVPCyDSPPp X-Received: by 2002:adf:df0b:0:b0:2ef:b139:5973 with SMTP id y11-20020adfdf0b000000b002efb1395973mr1048918wrl.17.1680865998881; Fri, 07 Apr 2023 04:13:18 -0700 (PDT) X-Google-Smtp-Source: AKy350Y1D5XyEBhaTjnWjn8ODLM2+ZhEW/9dJ/g2z84v/8imAJMUaNOuYt1mzrzwBQ0htzHvpcsSqw== X-Received: by 2002:adf:df0b:0:b0:2ef:b139:5973 with SMTP id y11-20020adfdf0b000000b002efb1395973mr1048887wrl.17.1680865998594; Fri, 07 Apr 2023 04:13:18 -0700 (PDT) Date: Fri, 7 Apr 2023 07:13:13 -0400 From: "Michael S. Tsirkin" To: Xuan Zhuo Cc: Wen Gu , Halil Pasic , virtio-comment@lists.oasis-open.org, hans@linux.alibaba.com, herongguang@linux.alibaba.com, zmlcc@linux.alibaba.com, dust.li@linux.alibaba.com, tonylu@linux.alibaba.com, zhenzao@linux.alibaba.com, helinguo@linux.alibaba.com, gerry@linux.alibaba.com, cohuck@redhat.com, jasowang@redhat.com, Jan Kiszka , kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com, hca@linux.ibm.com, twinkler@linux.ibm.com, raspl@linux.ibm.com, virtio-dev@lists.oasis-open.org, Alexandra Winter Message-ID: <20230407070820-mutt-send-email-mst@kernel.org> References: <20230209033056.96657-1-xuanzhuo@linux.alibaba.com> <20230209033056.96657-2-xuanzhuo@linux.alibaba.com> <20230323154656.7f036d52.pasic@linux.ibm.com> <7a9ebec0-5e87-b80f-4f2c-c4db7ae4fe84@linux.ibm.com> <20230405084632-mutt-send-email-mst@kernel.org> <1680837735.392044-2-xuanzhuo@linux.alibaba.com> MIME-Version: 1.0 In-Reply-To: <1680837735.392044-2-xuanzhuo@linux.alibaba.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: [virtio-dev] Re: [virtio-comment] Re: [virtio-dev] Re: [virtio-comment] [PATCH v3 1/1] virtio-ism: introduce new device virtio-ism On Fri, Apr 07, 2023 at 11:22:15AM +0800, Xuan Zhuo wrote: > On Wed, 5 Apr 2023 08:52:14 -0400, "Michael S. Tsirkin" wrote: > > On Wed, Apr 05, 2023 at 02:39:53PM +0200, Alexandra Winter wrote: > > > > > > > > > On 24.03.23 05:03, Wen Gu wrote: > > > > > > > > > > > > On 2023/3/23 22:46, Halil Pasic wrote: > > > > > > > >> On Thu,  9 Feb 2023 11:30:56 +0800 > > > >> Xuan Zhuo wrote: > > > >> > > > > > > ... > > > > > > > > > > >> To get back to the things proposed here: the cdid is IMHO > > > >> a nice thing, and is functionally corresponding to the > > > >> (S)EID. But it is 16 byte wide, and I have no idea how > > > >> is it supposed to be used in the CLC handshake. > > > >> > > > > > > > > CLC handshake carry one SEID for all the SMC-D device. Considering > > > > coexistence with ISM, I am not sure whether we can change or increase > > > > the SEID.. cc Alexandra > > > > > > > > Thanks! > > > > Wen Gu > > > > > > As mentioned by others, discussions are ongoing. > > > It would be great, if we can agree on a way to use the existing CLC handshake > > > for SMC-D via virtio-ism and ism-loopback. > > > In that case SEID needs to be unique per hardware instance, cannot be increased and > > > can only be changed for x86 in a non-colliding way. > > > > > > An alternative would be to define new a SMC-D(?) protocol variant/version, where we > > > are free to define new fields (e.g. UUIDs). > > > > > > Alexandra > > > > Problem with tying to hardware is that it is blocking > > migration (which is a challenge with ism anyway, but still). > > > We don't want to support migration. At least we don't want to support it for the > time being. Because there are indeed many problems. I think Migration is not > necessary for a new Virtio device. > > Thanks. The specific implementation does not matter much. At the spec level we strive to make interfaces generic so they can be reused down the road, rather than having to invent new ones for each use-case. Maybe we can come up with a way that let devices choose either an existing one with a SEID or a new one with a UUID? -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org