From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f49.google.com (mail-pa0-f49.google.com [209.85.220.49]) by dpdk.org (Postfix) with ESMTP id 583E211A2 for ; Wed, 30 Sep 2015 23:36:39 +0200 (CEST) Received: by padhy16 with SMTP id hy16so51804146pad.1 for ; Wed, 30 Sep 2015 14:36:38 -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:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=hvLYM8Pk6VioPc/pN+uJ26mMqaMl/8s69i4r6sTap8c=; b=W32dUY5PbJs8YlK8LIYPdDHfRi8AtHtozFLXiXCPyTPrlkgNEyyFmKJB79FOShxyVZ 1l8Ut8JsNhLwHbI4jfnxbkWUO63WvkRULXZuTlOY0eEoIrw76UGadJqO4eAETGAmymKD H1Ne2JLYb8ttmAVLrlDwqOcrjTtG5OSXrxCE3sy/zC/oM2jmyGSC8t9jU44TS3IjAyUF sgqqru322C6YAK+XdVNf0Zqz+Tmau6Gq+NhEp888C6yywapijXK+TbT1l3iQKDJjXGyN VdYp64MCL/IDqEJLR6hOPv+1lVzQPfEFaa8ugipOZ2WDbGXetZrYy4F9A0lVev77qyaw BYMw== X-Gm-Message-State: ALoCoQm0qIkKwklrPq5FEK0Lke3U+lR1xPL3SwI54nB5CJc2zwwhnwlb0xdNrzdHr3xtpsNZxwyR X-Received: by 10.66.235.67 with SMTP id uk3mr7683957pac.100.1443648998557; Wed, 30 Sep 2015 14:36:38 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id ya10sm2456261pbc.69.2015.09.30.14.36.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 Sep 2015 14:36:38 -0700 (PDT) Date: Wed, 30 Sep 2015 14:36:48 -0700 From: Stephen Hemminger To: Vlad Zolotarov Message-ID: <20150930143648.4b98db81@urahara> In-Reply-To: <560C417D.1050409@cloudius-systems.com> References: <20150930143927-mutt-send-email-mst@redhat.com> <560BCD2F.5060505@cloudius-systems.com> <20150930150115-mutt-send-email-mst@redhat.com> <560BD284.7040505@cloudius-systems.com> <20150930151632-mutt-send-email-mst@redhat.com> <560BDA81.6070807@cloudius-systems.com> <20150930182155-mutt-send-email-mst@redhat.com> <560C26DC.80209@cloudius-systems.com> <20150930215027-mutt-send-email-mst@redhat.com> <560C32CC.90708@cloudius-systems.com> <20150930222910-mutt-send-email-mst@redhat.com> <560C417D.1050409@cloudius-systems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" , "Michael S. Tsirkin" 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 21:36:39 -0000 On Wed, 30 Sep 2015 23:09:33 +0300 Vlad Zolotarov wrote: > > > On 09/30/15 22:39, Michael S. Tsirkin wrote: > > On Wed, Sep 30, 2015 at 10:06:52PM +0300, Vlad Zolotarov wrote: > >>>> How would iommu > >>>> virtualization change anything? > >>> Kernel can use an iommu to limit device access to memory of > >>> the controlling application. > >> Ok, this is obvious but what it has to do with enabling using MSI/MSI-X > >> interrupts support in uio_pci_generic? kernel may continue to limit the > >> above access with this support as well. > > It could maybe. So if you write a patch to allow MSI by at the same time > > creating an isolated IOMMU group and blocking DMA from device in > > question anywhere, that sounds reasonable. > > No, I'm only planning to add MSI and MSI-X interrupts support for > uio_pci_generic device. > The rest mentioned above should naturally be a matter of a different > patch and writing it is orthogonal to the patch I'm working on as has > been extensively discussed in this thread. > > > > I have a generic MSI and MSI-X driver (posted earlier on this list). About to post to upstream kernel.