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 X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 233D9CA9EC3 for ; Tue, 29 Oct 2019 16:27:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 01B0720717 for ; Tue, 29 Oct 2019 16:27:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390384AbfJ2Q1Y (ORCPT ); Tue, 29 Oct 2019 12:27:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55646 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390380AbfJ2Q1Y (ORCPT ); Tue, 29 Oct 2019 12:27:24 -0400 Received: from mail-wr1-f72.google.com (mail-wr1-f72.google.com [209.85.221.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id A013B5945B for ; Tue, 29 Oct 2019 16:27:23 +0000 (UTC) Received: by mail-wr1-f72.google.com with SMTP id v8so8741673wrt.16 for ; Tue, 29 Oct 2019 09:27:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=C6bDuPajdG9JVS65/nNfvWestag5Xwy94+uZABzDGas=; b=DTFMGWcFCSD5Lqs27RkZaHj9VxbGRS1duUJhSU/q3aIb1M0z/mqz4TQ2vnzjmbWZ2z 8YJQXNen+rxigeK96U6vljjp3Vc8B/mlquwzjwUtxKZDcu1RgKMu35Gp0AYMm9v4Kmdh 7jwbExEd2o7tIsj95Whw652DdTzFWvzBnaQpmr/W9h2fHZeZChl6cBl2KcNj8WRfHcBw 4k/Fu4VD+xmYD9oxW2BrqaeRIoG47RR9RhwF517QOJd8+YLNyjrNL69Q9mtLZpTEbmhg xt4ZyQerJ75kVS9IuFxrFZLKpLxrTpcK4EmuGsxsc2zPeOeon4oF3rog2JO9MeOuM7Hm RonA== X-Gm-Message-State: APjAAAWW4MvJqMSSmgETF6u7pVYNDVFWfW1NqkRLLUPy5yqx6ug/pRJ9 HoiqgeBtB+MTVpti1kcZcMotZtzLJLUMTQP3l7Re3AsmEeDsxJ0EXWHp1jK48fsQN5xvYQcaRO3 O2YWhvcL7HfUt1QOIbDsmpdfH X-Received: by 2002:a7b:c924:: with SMTP id h4mr5203728wml.143.1572366442238; Tue, 29 Oct 2019 09:27:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqwqcoHXB/eGlbAvP8/zQv1DhxCc9oHsJCpQ0Me1i12d1jrxIWteVIy4TZqjG4WQmNpAjkkq4g== X-Received: by 2002:a7b:c924:: with SMTP id h4mr5203696wml.143.1572366441980; Tue, 29 Oct 2019 09:27:21 -0700 (PDT) Received: from steredhat (94.222.26.109.rev.sfr.net. [109.26.222.94]) by smtp.gmail.com with ESMTPSA id v10sm4015055wmg.48.2019.10.29.09.27.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Oct 2019 09:27:21 -0700 (PDT) Date: Tue, 29 Oct 2019 17:27:12 +0100 From: Stefano Garzarella To: Stefan Hajnoczi , Adit Ranadive , Vishnu Dasa , Andy king , Aditya Sarwade , George Zhang , Jorgen Hansen Cc: netdev@vger.kernel.org, Sasha Levin , linux-hyperv@vger.kernel.org, Stephen Hemminger , Arnd Bergmann , kvm@vger.kernel.org, "Michael S. Tsirkin" , Greg Kroah-Hartman , Dexuan Cui , linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, Haiyang Zhang , Stefan Hajnoczi , "David S. Miller" Subject: Re: [PATCH net-next 00/14] vsock: add multi-transports support Message-ID: <20191029162712.fn5rgxrwdrbxuehw@steredhat> References: <20191023095554.11340-1-sgarzare@redhat.com> <20191027080146.GA4472@stefanha-x1.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191027080146.GA4472@stefanha-x1.localdomain> User-Agent: NeoMutt/20180716 Sender: linux-hyperv-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org On Sun, Oct 27, 2019 at 09:01:46AM +0100, Stefan Hajnoczi wrote: > On Wed, Oct 23, 2019 at 11:55:40AM +0200, Stefano Garzarella wrote: > > This series adds the multi-transports support to vsock, following > > this proposal: https://www.spinics.net/lists/netdev/msg575792.html > > > > With the multi-transports support, we can use VSOCK with nested VMs > > (using also different hypervisors) loading both guest->host and > > host->guest transports at the same time. > > Before this series, vmci-transport supported this behavior but only > > using VMware hypervisor on L0, L1, etc. > > > > RFC: https://patchwork.ozlabs.org/cover/1168442/ > > RFC -> v1: > > - Added R-b/A-b from Dexuan and Stefan > > - Fixed comments and typos in several patches (Stefan) > > - Patch 7: changed .notify_buffer_size return to void (Stefan) > > - Added patch 8 to simplify the API exposed to the transports (Stefan) > > - Patch 11: > > + documented VSOCK_TRANSPORT_F_* flags (Stefan) > > + fixed vsock_assign_transport() when the socket is already assigned > > + moved features outside of struct vsock_transport, and used as > > parameter of vsock_core_register() as a preparation of Patch 12 > > - Removed "vsock: add 'transport_hg' to handle g2h\h2g transports" patch > > - Added patch 12 to register vmci_transport only when VMCI guest/host > > are active > > Has there been feedback from Jorgen or someone else from VMware? A > Reviewed-by or Acked-by would be nice since this patch series affects > VMCI AF_VSOCK. > Unfortunately not for now, I'm adding to this thread some VMware guys that reviewed latest vmci patches. Would be nice to have your feedback for these changes. Thanks in advance, Stefano