From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753954AbdHRCye (ORCPT ); Thu, 17 Aug 2017 22:54:34 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56518 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753856AbdHRCyd (ORCPT ); Thu, 17 Aug 2017 22:54:33 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com A00B14E341 Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx09.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mst@redhat.com Date: Fri, 18 Aug 2017 05:54:26 +0300 From: "Michael S. Tsirkin" To: Auger Eric Cc: Will Deacon , eric.auger.pro@gmail.com, iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org, robin.murphy@arm.com, Jean-Philippe.Brucker@arm.com, christoffer.dall@linaro.org, Marc.Zyngier@arm.com, alex.williamson@redhat.com, peterx@redhat.com, tn@semihalf.com, bharat.bhushan@nxp.com Subject: Re: [RFC v2 2/4] iommu/arm-smmu-v3: Add tlbi_on_map option Message-ID: <20170818055031-mutt-send-email-mst@kernel.org> References: <1502459130-6234-1-git-send-email-eric.auger@redhat.com> <1502459130-6234-3-git-send-email-eric.auger@redhat.com> <20170817163424.GC30719@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Fri, 18 Aug 2017 02:54:33 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 17, 2017 at 07:47:04PM +0200, Auger Eric wrote: > I will see with Peter and other potential users in the community whether > it is worth to pursue the efforts on upstreaming the QEMU vSMMUv3 > device, considering the VFIO/VHOST integration is made impossible. I posted more ideas on finding a way to support it after all separately. Even without this: 1. VHOST does not need to be notified on map. 2. VFIO might be possible for hardware that supports nested page tables. IMHO 2 is worth looking into. -- MST