From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Allain Legacy <allain.legacy@windriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] igb_uio: support devices with at least 1 bar defined
Date: Tue, 14 Mar 2017 16:59:07 +0000 [thread overview]
Message-ID: <ec0bd08f-81b3-b27e-9dd5-f4e86900a2ad@intel.com> (raw)
In-Reply-To: <1489509189-166941-1-git-send-email-allain.legacy@windriver.com>
On 3/14/2017 4:33 PM, Allain Legacy wrote:
> From: Matt Peters <matt.peters@windriver.com>
>
> Allow the BAR setup to succeed if a device has at least 1 BAR region
> defined. Previously, the device probe would only succeed if at least one
> memory BAR existed, but there are devices that have only port I/O BARs.
>
> For example, on Virtual Box a virtio device has only a single I/O BAR
> because by default MSI-X is not enabled. While in qemu/kvm the virtio
> device has MSI-X enabled and therefore has both an I/O and Memory BAR.
>
> The following are excerpts from "lspci -nnvvvv -s 00:09.0" on both types of
> systems.
>
> Virtual Box:
>
> Region 0: I/O ports at d260 [size=32]
> Capabilities: [80] #00 [0000]
>
> QEMU/KVM:
>
> Region 0: I/O ports at c060 [size=32]
> Region 1: Memory at febd1000 (32-bit, non-prefetchable) [size=4K]
> Expansion ROM at feb80000 [disabled] [size=256K]
> Capabilities: [40] MSI-X: Enable+ Count=3 Masked-
> Vector table: BAR=1 offset=00000000
> PBA: BAR=1 offset=00000800
>
> Signed-off-by: Matt Peters <matt.peters@windriver.com>
> Signed-off-by: Allain Legacy <allain.legacy@windriver.com>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2017-03-14 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 16:33 Allain Legacy
2017-03-14 16:59 ` Ferruh Yigit [this message]
2017-03-15 13:01 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ec0bd08f-81b3-b27e-9dd5-f4e86900a2ad@intel.com \
--to=ferruh.yigit@intel.com \
--cc=allain.legacy@windriver.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).