From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) by dpdk.org (Postfix) with ESMTP id E4753A6A for ; Wed, 30 Sep 2015 22:09:35 +0200 (CEST) Received: by wicfx3 with SMTP id fx3so3309009wic.1 for ; Wed, 30 Sep 2015 13:09:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=ViwWE3AVqsLc6fAgoru3BdkFNn8xck732j4UT66n93E=; b=bYHvfj9+5zo9bC5ynHTMh7UUxEVZbBSaSJszgRnl1htsgw+HEGRGjJDWW+UfQCzbYY 7SK0J9S8nLC9WKUK0f5djeR3Di5sQyB1l2BBFM8ZdWZpVZyxcjPeUbmxyXV6SEO28ZTR dnOQKoPe1EWby8PV07irmMSN7F03s0bDDI9xHBpeTlTl3EKGR5GTTfLiFgNYiF9c7WIa 49/PsJ/1vRxhASYVS5kFoTSuijqspO+hTV8jt03BlG3+h6M4+HE9XaWf0KqcipRNUdwH CRA+6HOEApftWxd62JT23dv8pKc7B8+X/5NzvXo8VUf/7cs43hTXSgVZzFvUEA5eh7bP KkfA== X-Gm-Message-State: ALoCoQnl+SxwV/pvaZfezWNyw3Ra4klfmpz0Kt232TziuRip7mum97XKhXVuvbdmDQppNLbW/mW7 X-Received: by 10.180.11.212 with SMTP id s20mr6773586wib.40.1443643775754; Wed, 30 Sep 2015 13:09:35 -0700 (PDT) Received: from [10.0.0.2] (bzq-79-180-197-252.red.bezeqint.net. [79.180.197.252]) by smtp.googlemail.com with ESMTPSA id gc8sm31302279wib.2.2015.09.30.13.09.34 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 30 Sep 2015 13:09:35 -0700 (PDT) To: "Michael S. Tsirkin" 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> From: Vlad Zolotarov Message-ID: <560C417D.1050409@cloudius-systems.com> Date: Wed, 30 Sep 2015 23:09:33 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20150930222910-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 20:09:36 -0000 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. >