From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Harton <dharton@cisco.com>,
dev@dpdk.org, mw@semihalf.com, mk@semihalf.com,
gtzalik@amazon.com, evgenys@amazon.com, igorch@amazon.com
Subject: Re: [dpdk-dev] [PATCH] net/ena: initialize PCI info in eth_ena_dev_init
Date: Thu, 12 Dec 2019 14:53:56 +0000 [thread overview]
Message-ID: <d0e0a8d9-0392-6ed5-310e-b632c4bbe16e@intel.com> (raw)
In-Reply-To: <20191210223726.19698-1-dharton@cisco.com>
On 12/10/2019 10:37 PM, David Harton wrote:
> Network drivers were originally modified to initialize PCI info with
> commit eeefe73f0af1 ("drivers: copy PCI device info to ethdev data").
> Modifying net/ena to conform.
>
> Signed-off-by: David Harton <dharton@cisco.com>
> ---
> drivers/net/ena/ena_ethdev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/ena/ena_ethdev.c b/drivers/net/ena/ena_ethdev.c
> index 7d4a3b225..4170cf749 100644
> --- a/drivers/net/ena/ena_ethdev.c
> +++ b/drivers/net/ena/ena_ethdev.c
> @@ -1701,6 +1701,7 @@ static int eth_ena_dev_init(struct rte_eth_dev *eth_dev)
> adapter->rte_dev = eth_dev;
>
> pci_dev = RTE_ETH_DEV_TO_PCI(eth_dev);
> + rte_eth_copy_pci_info(eth_dev, pci_dev);
> adapter->pdev = pci_dev;
>
> PMD_INIT_LOG(INFO, "Initializing %x:%x:%x.%d",
>
Hi David,
Is it really needed, since it should be called by API already [1], what field in
eth_dev was missing?
[1]
eth_ena_pci_probe()
rte_eth_dev_pci_generic_probe(eth_ena_dev_init)
rte_eth_dev_pci_allocate()
rte_eth_copy_pci_info()
eth_ena_dev_init()
next prev parent reply other threads:[~2019-12-12 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 22:37 David Harton
2019-12-11 8:45 ` Michał Krawczyk
2019-12-12 14:53 ` Ferruh Yigit [this message]
2019-12-12 15:52 ` David Harton (dharton)
-- strict thread matches above, loose matches on Subject: below --
2019-12-10 22:18 David Harton
2019-12-10 22:13 David Harton
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=d0e0a8d9-0392-6ed5-310e-b632c4bbe16e@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=dharton@cisco.com \
--cc=evgenys@amazon.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.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).