From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 39AEE1B3A4
 for <dev@dpdk.org>; Thu,  4 Oct 2018 00:40:09 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id DA3C021E6D;
 Wed,  3 Oct 2018 18:40:08 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162])
 by compute1.internal (MEProxy); Wed, 03 Oct 2018 18:40:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 from:to:cc:subject:date:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding:content-type; s=mesmtp;
 bh=xsIjY0uoPfSX8UiFJQbxs7KCMU6T7u8Ib/iYjTI5/k8=; b=QxrBU8ZmcA9b
 2UzUVlxepA6+XV5f8iw8xqYdr5RnSML8YqVzmVIijiNbnJGL5MjiesOB9qptXU6D
 8r/OX0JrIipzL5jkHJufRRwASriIf1xwrwrZvDXomVOntrV0/FYx7WmRsDM8g+gV
 7hTURkvrmqWJLLmi9G9smkbVbvRS7Nw=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm3; bh=xsIjY0uoPfSX8UiFJQbxs7KCMU6T7u8Ib/iYjTI5/
 k8=; b=MRpopfiDuIuNRByulKF8y+q/YnPPbOeRmeuN1uPsbQ7gNZbarF9zVZ53d
 Z3xCGX8bjwPeG33ah2hZC7fQs9jPCSTS8asIwAt2Xy5UbLODS786Y+Qh2KHKIjQE
 Xlq0bCIA2VAQi1wQeSPpbwkQ25bux0rvMK7lzlB3g6PZP29TRtPzLmTvW4G+ggwa
 klOS2MvVDqA7P1ZKdliXM3SU4iTFu8KS6icYlB7jxY661e9KrzdSMwY2F0/iOGyT
 jkd2BFGpYpXj/VH7R+TGN9DEVa/er4GbHtI4cn6DPs+i7yK2iV0pGtaY8f4BaVlj
 ApxUvDqU+BI6G4fWf2j8xA5KRXJdQ==
X-ME-Sender: <xms:SEW1W1lp0PnI2sbo9HHUhPQjmhYK3_OhoUgH-OM6CpFTl1Ll9GcrvQ>
X-ME-Proxy: <xmx:SEW1W0Oxnj5FWTsjzlZJsEEtuwjK3bCBtm4FJsxKG2nS9lvznal7Bw>
 <xmx:SEW1W3siB-cEAXF2SxdmP6mHqavqlTN2yAp4uvg9UYYEMU7jC7pYWQ>
 <xmx:SEW1W23LgJFDOoFdwrE-qnrCFJeFPCQEn9HUZhd7pq0jfF0VKSAhDw>
 <xmx:SEW1Wy2XJgyTorEmtt-kbPz7iO-jZE8fA_OCEE-ZvWNsc6uKGsNCmA>
 <xmx:SEW1W7ZMnjMU5cOizRRUeMLLUXb3gdUuz84Qte5c-ADpzJ5q20xcMA>
 <xmx:SEW1W-NPYdl4JQx-U6fmIZHEmH2OqsHNVQNGHIslzXWZD_6ddUlNMQ>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 7D475E4123;
 Wed,  3 Oct 2018 18:40:07 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, t.yoshimura8869@gmail.com, jerin.jacob@caviumnetworks.com
Date: Thu, 04 Oct 2018 00:40:06 +0200
Message-ID: <2189000.I1ypxTDmWI@xps>
In-Reply-To: <ae23cc3f53af9edc3e1fd74b1745c5bcd167e127.1537448866.git.anatoly.burakov@intel.com>
References: <35b0d3fcf990a064a94dc93d834d86352603de98.1533036456.git.anatoly.burakov@intel.com>
 <ae23cc3f53af9edc3e1fd74b1745c5bcd167e127.1537448866.git.anatoly.burakov@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v3] pci/vfio: allow mapping MSI-X BARs if
	kernel allows it
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 22:40:09 -0000

20/09/2018 15:11, Anatoly Burakov:
> Currently, DPDK will skip mapping some areas (or even an entire BAR)
> if MSI-X table happens to be in them but is smaller than page size.
> 
> Kernels 4.16+ will allow mapping MSI-X BARs [1], and will report this
> as a capability flag. Capability flags themselves are also only
> supported since kernel 4.6 [2].
> 
> This commit will introduce support for checking VFIO capabilities,
> and will use it to check if we are allowed to map BARs with MSI-X
> tables in them, along with backwards compatibility for older
> kernels, including a workaround for a variable rename in VFIO
> region info structure [3].
> 
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
> linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6
> 
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
> linux.git/commit/?id=c84982adb23bcf3b99b79ca33527cd2625fbe279
> 
> [3] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/
> linux.git/commit/?id=ff63eb638d63b95e489f976428f1df01391e15e4
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>

Applied, thanks