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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B5150C433F5 for ; Wed, 10 Nov 2021 07:12:49 +0000 (UTC) Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5089A60724 for ; Wed, 10 Nov 2021 07:12:49 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 5089A60724 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id 05108608FE; Wed, 10 Nov 2021 07:12:49 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CLwlZktZT-o2; Wed, 10 Nov 2021 07:12:48 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [140.211.9.56]) by smtp3.osuosl.org (Postfix) with ESMTPS id 9215D608D4; Wed, 10 Nov 2021 07:12:47 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id 6904FC0012; Wed, 10 Nov 2021 07:12:47 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 8BFCEC000E for ; Wed, 10 Nov 2021 07:12:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 62B4140259 for ; Wed, 10 Nov 2021 07:12:46 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u58PfINqsH_j for ; Wed, 10 Nov 2021 07:12:45 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by smtp2.osuosl.org (Postfix) with ESMTPS id 3952D400DE for ; Wed, 10 Nov 2021 07:12:44 +0000 (UTC) X-IronPort-AV: E=McAfee;i="6200,9189,10163"; a="230081715" X-IronPort-AV: E=Sophos;i="5.87,223,1631602800"; d="scan'208,217";a="230081715" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Nov 2021 23:12:41 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.87,223,1631602800"; d="scan'208,217";a="669693531" Received: from orsmsx603.amr.corp.intel.com ([10.22.229.16]) by orsmga005.jf.intel.com with ESMTP; 09 Nov 2021 23:12:40 -0800 Received: from orsmsx612.amr.corp.intel.com (10.22.229.25) by ORSMSX603.amr.corp.intel.com (10.22.229.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.12; Tue, 9 Nov 2021 23:12:40 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by ORSMSX612.amr.corp.intel.com (10.22.229.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.12; Tue, 9 Nov 2021 23:12:39 -0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.2242.012; Wed, 10 Nov 2021 15:12:36 +0800 From: "Wang, Wei W" To: "sgarzare@redhat.com" , "davem@davemloft.net" , "kuba@kernel.org" , Stefan Hajnoczi , "mst@redhat.com" , Paolo Bonzini , "kys@microsoft.com" , "linux-kernel@vger.kernel.org" , "virtualization@lists.linux-foundation.org" Subject: [RFC] hypercall-vsock: add a new vsock transport Thread-Topic: [RFC] hypercall-vsock: add a new vsock transport Thread-Index: AdfR7PQwhDKKIu84SJaS6/iA/MsV5g== Date: Wed, 10 Nov 2021 07:12:36 +0000 Message-ID: <71d7b0463629471e9d4887d7fcef1d8d@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-reaction: no-action dlp-version: 11.6.200.16 x-originating-ip: [10.239.127.36] MIME-Version: 1.0 Cc: "Yamahata, Isaku" , "Kleen, Andi" X-BeenThere: virtualization@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Linux virtualization List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1182963909694896001==" Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" --===============1182963909694896001== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_71d7b0463629471e9d4887d7fcef1d8dintelcom_" --_000_71d7b0463629471e9d4887d7fcef1d8dintelcom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, We plan to add a new vsock transport based on hypercall (e.g. vmcall on Int= el CPUs). It transports AF_VSOCK packets between the guest and host, which is similar= to virtio-vsock, vmci-vsock and hyperv-vsock. Compared to the above listed vsock transports which are designed for high p= erformance, the main advantages of hypercall-vsock are: 1) It is VMM agnostic. For example, one guest working on hypercall-vs= ock can run on either KVM, Hyperv, or VMware. 2) It is simpler. It doesn't rely on any complex bus enumeration (e.g. virtio-pci based vsock device may need the whole implementation of PC= I). An example usage is the communication between MigTD and host (Page 8 at https://static.sched.com/hosted_files/kvmforum2021/ef/TDX%20Live%20Migratio= n_Wei%20Wang.pdf). MigTD communicates to host to assist the migration of the target (user) TD. MigTD is part of the TCB, so its implementation is expected to be as simple= as possible (e.g. bare mental implementation without OS, no PCI driver support). Looking forward to your feedbacks. Thanks, Wei --_000_71d7b0463629471e9d4887d7fcef1d8dintelcom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,<= o:p>

 

We p= lan to add a new vsock transport based on hypercall (e.g. vmcall on Intel C= PUs).

It t= ransports AF_VSOCK packets between the guest and host, which is similar to<= o:p>

virt= io-vsock, vmci-vsock and hyperv-vsock.

 

Comp= ared to the above listed vsock transports which are designed for high perfo= rmance,

the = main advantages of hypercall-vsock are:

1)       It is VMM agnostic. For example, one guest working on hypercall-vsock c= an run on

= either KVM, Hyperv, or VMwa= re.

2)       It is simpler. It doesn’t rely on any complex bus enumeration

= (e.g. virtio-pci based vsoc= k device may need the whole implementation of PCI).

 

An e= xample usage is the communication between MigTD and host (Page 8 at

https://static.sched.com/hosted_files/kvmforum2021= /ef/TDX%20Live%20Migration_Wei%20Wang.pdf).

MigT= D communicates to host to assist the migration of the target (user) TD.

MigT= D is part of the TCB, so its implementation is expected to be as simple as = possible

(e.g= . bare mental implementation without OS, no PCI driver support).=

 

Look= ing forward to your feedbacks.

 

Than= ks,

Wei<= o:p>

--_000_71d7b0463629471e9d4887d7fcef1d8dintelcom_-- --===============1182963909694896001== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization --===============1182963909694896001==--