From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by dpdk.org (Postfix) with ESMTP id D45D48DB0 for ; Wed, 30 Sep 2015 19:44:55 +0200 (CEST) Received: by wicgb1 with SMTP id gb1so206216142wic.1 for ; Wed, 30 Sep 2015 10:44:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to; bh=7lp8aT1sktmM0viKQOMzfMonmIJVM5gGYwkhVIeAVFQ=; b=A030ZLtzMImpyCn/p8ZSCycDcFPXM4hfD4BhLS/iWu5GAWa13W/NxmBR1eXrHFu9zt YtkFCTncnwEgRqiBTboO1wUUhUBguHqnDgwOWt2ZYXeCStwJbp49htsCkmt+JmhfBK7p I/hrVL6YDQ4SPFfd86eny58Z4jCXhJeCJe8O5Z2oatYF6T7V3kNZoanE7UsJxtNGYUi6 b5Ss+8N1IUcFo+HJuZ7R+Bo8O49H5rraypbZMzRWCQF79CqmV/S1e4N6PH6x+eJHyPsi FgQ0umotrsSCv1cgMvAkEZR6vMl2mdY6gzZxRifM2rbLUyumg6ItAuevJFro2nXQnaoK Zv7w== X-Gm-Message-State: ALoCoQnQljOYZpfHtcYhtDG8w5rYqEiUKIwSlo2ykUNT9TlrtvEqzGAlkOBboSIQfZDBCG5xqGav X-Received: by 10.180.105.135 with SMTP id gm7mr31722619wib.18.1443635095700; Wed, 30 Sep 2015 10:44:55 -0700 (PDT) Received: from trex.cloudius-systems.com (bzq-84-111-155-225.red.bezeqint.net. [84.111.155.225]) by smtp.gmail.com with ESMTPSA id bf8sm1797251wjc.22.2015.09.30.10.44.54 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Sep 2015 10:44:55 -0700 (PDT) Received: by trex.cloudius-systems.com (Postfix, from userid 1042) id 3C4C283F52; Wed, 30 Sep 2015 20:44:46 +0300 (IDT) Date: Wed, 30 Sep 2015 20:44:46 +0300 From: Gleb Natapov To: "Michael S. Tsirkin" Message-ID: <20150930174446.GB27881@scylladb.com> References: <56079527.3000802@cloudius-systems.com> <20150927123914-mutt-send-email-mst@redhat.com> <560ABF25.9030300@cloudius-systems.com> <20150929235122-mutt-send-email-mst@redhat.com> <20150929144616.4e70b44c@urahara> <20150930004714-mutt-send-email-mst@redhat.com> <560BBB62.3050502@cloudius-systems.com> <20150930102807.6e681bca@urahara> <20150930203712-mutt-send-email-mst@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150930203712-mutt-send-email-mst@redhat.com> Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Having troubles binding an SR-IOV VF to uio_pci_generic on Amazon instance X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2015 17:44:56 -0000 On Wed, Sep 30, 2015 at 08:39:43PM +0300, Michael S. Tsirkin wrote: > On Wed, Sep 30, 2015 at 10:28:07AM -0700, Stephen Hemminger wrote: > > On Wed, 30 Sep 2015 13:37:22 +0300 > > Vlad Zolotarov wrote: > > > > > > > > > > > On 09/30/15 00:49, Michael S. Tsirkin wrote: > > > > On Tue, Sep 29, 2015 at 02:46:16PM -0700, Stephen Hemminger wrote: > > > >> On Tue, 29 Sep 2015 23:54:54 +0300 > > > >> "Michael S. Tsirkin" wrote: > > > >> > > > >>> On Tue, Sep 29, 2015 at 07:41:09PM +0300, Vlad Zolotarov wrote: > > > >>>> The security breach motivation u brought in "[RFC PATCH] uio: > > > >>>> uio_pci_generic: Add support for MSI interrupts" thread seems a bit weak > > > >>>> since one u let the userland access to the bar it may do any funny thing > > > >>>> using the DMA engine of the device. This kind of stuff should be prevented > > > >>>> using the iommu and if it's enabled then any funny tricks using MSI/MSI-X > > > >>>> configuration will be prevented too. > > > >>>> > > > >>>> I'm about to send the patch to main Linux mailing list. Let's continue this > > > >>>> discussion there. > > > >>>> > > > >>> Basically UIO shouldn't be used with devices capable of DMA. > > > >>> Use VFIO for that (yes, this implies an emulated or PV IOMMU). > > > > > > If there is an IOMMU in the picture there shouldn't be any problem to > > > use UIO with DMA capable devices. > > > > > > >>> I don't think this can change. > > > >> Given there is no PV IOMMU and even if there was it would be too slow for DPDK > > > >> use, I can't accept that. > > > > QEMU does allow emulating an iommu. > > > > > > Amazon's EC2 xen HV doesn't. At least today. Therefore VFIO is not an > > > option there. And again, it's a general issue not DPDK specific. > > > Today one has to develop some proprietary modules (like igb_uio) to > > > workaround the issue and this is lame. IMHO uio_pci_generic should > > > be fixed to be able to properly work within any virtualized environment > > > and not only with KVM. > > > > > > > Also VMware (bigger problem) has no IOMMU emulation. > > Other environments as well (Windriver, GCE) have noe IOMMU. > > Because the use-case of userspace drivers is not important enough? Because "secure" userspace drivers is not important enough. > Without an IOMMU, there's no way to have secure userspace drivers. > People use VMs as an application containers, not as a machine that needs to be secured for multiuser scenario. -- Gleb.