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=-5.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable 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 50B16FA372C for ; Thu, 7 Nov 2019 04:16:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 24DE82166E for ; Thu, 7 Nov 2019 04:16:29 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="Do3Igs2t" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733160AbfKGEQ0 (ORCPT ); Wed, 6 Nov 2019 23:16:26 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:55556 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1733080AbfKGEQ0 (ORCPT ); Wed, 6 Nov 2019 23:16:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1573100185; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=k3IbSyGD4qLkNAVSZEuvxBFa8ZkDMuEWAdZpi7gSPzg=; b=Do3Igs2tvwS8OTK8hbB7u4ZsqRcVAkIVIUg14UFpmEe4B+9+JqeyLJxNAC1Nw1+YzDeDlC fyCofOhZlkeDIGBo0xlhAC9tu+ECYZ235RWfm3U651u2soB6+FL+y6wYAcUU9EL9+bBR/4 LC7dukr1sDz0p+VtiwMPTnGGZVF84UM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-341-MQBzENQcOFypmSyLPrCApQ-1; Wed, 06 Nov 2019 23:16:17 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C3470800C61; Thu, 7 Nov 2019 04:16:15 +0000 (UTC) Received: from [10.72.12.214] (ovpn-12-214.pek2.redhat.com [10.72.12.214]) by smtp.corp.redhat.com (Postfix) with ESMTP id 54F865D6B7; Thu, 7 Nov 2019 04:16:03 +0000 (UTC) Subject: Re: [PATCH v5] vhost: introduce mdev based hardware backend To: Tiwei Bie , "Michael S. Tsirkin" Cc: alex.williamson@redhat.com, maxime.coquelin@redhat.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, virtualization@lists.linux-foundation.org, netdev@vger.kernel.org, dan.daly@intel.com, cunming.liang@intel.com, zhihong.wang@intel.com, lingshan.zhu@intel.com References: <20191105115332.11026-1-tiwei.bie@intel.com> <20191106075733-mutt-send-email-mst@kernel.org> <20191106143907.GA10776@___> From: Jason Wang Message-ID: Date: Thu, 7 Nov 2019 12:16:01 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20191106143907.GA10776@___> Content-Language: en-US X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-MC-Unique: MQBzENQcOFypmSyLPrCApQ-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 2019/11/6 =E4=B8=8B=E5=8D=8810:39, Tiwei Bie wrote: > On Wed, Nov 06, 2019 at 07:59:02AM -0500, Michael S. Tsirkin wrote: >> On Tue, Nov 05, 2019 at 07:53:32PM +0800, Tiwei Bie wrote: >>> This patch introduces a mdev based hardware vhost backend. >>> This backend is built on top of the same abstraction used >>> in virtio-mdev and provides a generic vhost interface for >>> userspace to accelerate the virtio devices in guest. >>> >>> This backend is implemented as a mdev device driver on top >>> of the same mdev device ops used in virtio-mdev but using >>> a different mdev class id, and it will register the device >>> as a VFIO device for userspace to use. Userspace can setup >>> the IOMMU with the existing VFIO container/group APIs and >>> then get the device fd with the device name. After getting >>> the device fd, userspace can use vhost ioctls on top of it >>> to setup the backend. >>> >>> Signed-off-by: Tiwei Bie >> So at this point, looks like the only thing missing is IFC, and then all >> these patches can go in. >> But as IFC is still being worked on anyway, it makes sense to >> address the minor comments manwhile so we don't need >> patches on top. >> Right? > Yeah, of course. > > Thanks, > Tiwei Please send V6 and I will ack there. Thanks