From: Ranjit Menon <ranjit.menon@intel.com>
To: Khoa To <khot@linux.microsoft.com>, dev@dpdk.org
Cc: dmitry.kozliuk@gmail.com, pallavi.kadam@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] bus/pci/windows: support for PCI scan allowed and blocked lists
Date: Thu, 18 Feb 2021 10:53:54 -0800 [thread overview]
Message-ID: <2da301ca-f163-97a7-692d-2cfeecf819bd@intel.com> (raw)
In-Reply-To: <1613673602-6291-1-git-send-email-khot@linux.microsoft.com>
Hi Khoa,
On 2/18/2021 10:40 AM, Khoa To wrote:
> EAL -a and -b options are used to specify which PCI devices are
> explicitly allowed or blocked during PCI bus scan. This evaluation
> is missing in the Windows implementation of rte_pci_scan.
> This patch provides this missing functionality, so that apps can specify
> which NetUIO devices to ignore during PCI bus scan.
>
> Signed-off-by: Khoa To <khot@linux.microsoft.com>
> ---
>
> v2:
> * Truncate commit description lines to 75 charaters or less
>
>
> drivers/bus/pci/windows/pci.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/bus/pci/windows/pci.c b/drivers/bus/pci/windows/pci.c
> index f66258452..0bba05eb4 100644
> --- a/drivers/bus/pci/windows/pci.c
> +++ b/drivers/bus/pci/windows/pci.c
> @@ -396,6 +396,7 @@ rte_pci_scan(void)
> DWORD device_index = 0, found_device = 0;
> HDEVINFO dev_info;
> SP_DEVINFO_DATA device_info_data;
> + struct rte_pci_addr addr;
>
> /* for debug purposes, PCI can be disabled */
> if (!rte_eal_has_pci())
> @@ -420,6 +421,13 @@ rte_pci_scan(void)
> &GUID_DEVCLASS_NET) ||
> IsEqualGUID(&(device_info_data.ClassGuid),
> &GUID_DEVCLASS_NETUIO)) {
> +
> + if (get_device_pci_address(dev_info, &device_info_data, &addr) != 0)
> + continue;
> +
> + if (rte_pci_ignore_device(&addr))
> + continue;
> +
> ret = pci_scan_one(dev_info, &device_info_data);
> if (ret == ERROR_SUCCESS)
> found_device++;
I think this change can be made inside the pci_scan_one() function where
we already call
get_device_pci_address().
ranjit m.
next prev parent reply other threads:[~2021-02-18 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 5:40 [dpdk-dev] [PATCH] " Khoa To
2021-02-18 18:40 ` [dpdk-dev] [PATCH v2] " Khoa To
2021-02-18 18:53 ` Ranjit Menon [this message]
2021-02-18 21:23 ` Dmitry Kozlyuk
2021-03-01 6:22 ` [dpdk-dev] [PATCH v3] " Khoa To
2021-03-01 6:52 ` [dpdk-dev] [PATCH v4] " Khoa To
2021-03-04 0:21 ` Ranjit Menon
2021-03-04 0:26 ` Khoa To
2021-03-04 7:14 ` Dmitry Kozlyuk
2021-03-16 21:35 ` 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=2da301ca-f163-97a7-692d-2cfeecf819bd@intel.com \
--to=ranjit.menon@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=khot@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
/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).