* [dpdk-dev] [PATCH] app/test-pmd: fix rte_pci_tailq not initialized before used
@ 2015-03-11 8:43 Yong Liu
2015-03-11 8:59 ` David Marchand
0 siblings, 1 reply; 3+ messages in thread
From: Yong Liu @ 2015-03-11 8:43 UTC (permalink / raw)
To: dev
Function rte_eal_pci_init will cast pci resource list and used for insert
probed device later. But all tailq initialized in function
rte_eal_tailqs_init, so rte_eal_pci_init must be called after it.
Signed-off-by: Marvin Liu <yong.liu@intel.com>
diff --git a/lib/librte_eal/linuxapp/eal/eal.c b/lib/librte_eal/linuxapp/eal/eal.c
index bd770cf..576f9f8 100644
--- a/lib/librte_eal/linuxapp/eal/eal.c
+++ b/lib/librte_eal/linuxapp/eal/eal.c
@@ -755,9 +755,6 @@ rte_eal_init(int argc, char **argv)
rte_config_init();
- if (rte_eal_pci_init() < 0)
- rte_panic("Cannot init PCI\n");
-
#ifdef RTE_LIBRTE_IVSHMEM
if (rte_eal_ivshmem_init() < 0)
rte_panic("Cannot init IVSHMEM\n");
@@ -792,6 +789,9 @@ rte_eal_init(int argc, char **argv)
if (rte_eal_timer_init() < 0)
rte_panic("Cannot init HPET or TSC timers\n");
+ if (rte_eal_pci_init() < 0)
+ rte_panic("Cannot init PCI\n");
+
eal_check_mem_on_local_socket();
rte_eal_mcfg_complete();
--
1.9.3
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [PATCH] app/test-pmd: fix rte_pci_tailq not initialized before used
2015-03-11 8:43 [dpdk-dev] [PATCH] app/test-pmd: fix rte_pci_tailq not initialized before used Yong Liu
@ 2015-03-11 8:59 ` David Marchand
2015-03-11 17:26 ` David Marchand
0 siblings, 1 reply; 3+ messages in thread
From: David Marchand @ 2015-03-11 8:59 UTC (permalink / raw)
To: Yong Liu; +Cc: dev
Hello Marvin,
I think this fix will break ivshmem init.
pci_init was moved when introducing ivshmem_init.
If you have a setup for this, can you check ivshmem init with your fix ?
Thanks.
--
David Marchand
On Wed, Mar 11, 2015 at 9:43 AM, Yong Liu <yong.liu@intel.com> wrote:
> Function rte_eal_pci_init will cast pci resource list and used for insert
> probed device later. But all tailq initialized in function
> rte_eal_tailqs_init, so rte_eal_pci_init must be called after it.
>
> Signed-off-by: Marvin Liu <yong.liu@intel.com>
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal.c
> b/lib/librte_eal/linuxapp/eal/eal.c
> index bd770cf..576f9f8 100644
> --- a/lib/librte_eal/linuxapp/eal/eal.c
> +++ b/lib/librte_eal/linuxapp/eal/eal.c
> @@ -755,9 +755,6 @@ rte_eal_init(int argc, char **argv)
>
> rte_config_init();
>
> - if (rte_eal_pci_init() < 0)
> - rte_panic("Cannot init PCI\n");
> -
> #ifdef RTE_LIBRTE_IVSHMEM
> if (rte_eal_ivshmem_init() < 0)
> rte_panic("Cannot init IVSHMEM\n");
> @@ -792,6 +789,9 @@ rte_eal_init(int argc, char **argv)
> if (rte_eal_timer_init() < 0)
> rte_panic("Cannot init HPET or TSC timers\n");
>
> + if (rte_eal_pci_init() < 0)
> + rte_panic("Cannot init PCI\n");
> +
> eal_check_mem_on_local_socket();
>
> rte_eal_mcfg_complete();
> --
> 1.9.3
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [PATCH] app/test-pmd: fix rte_pci_tailq not initialized before used
2015-03-11 8:59 ` David Marchand
@ 2015-03-11 17:26 ` David Marchand
0 siblings, 0 replies; 3+ messages in thread
From: David Marchand @ 2015-03-11 17:26 UTC (permalink / raw)
To: Yong Liu; +Cc: dev
On Wed, Mar 11, 2015 at 9:59 AM, David Marchand <david.marchand@6wind.com>
wrote:
> Hello Marvin,
>
> I think this fix will break ivshmem init.
> pci_init was moved when introducing ivshmem_init.
>
> If you have a setup for this, can you check ivshmem init with your fix ?
>
> Thanks.
>
I just posted a different fix.
If yours breaks ivshmem, please test mine.
Thanks.
--
David Marchand
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-03-11 17:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-11 8:43 [dpdk-dev] [PATCH] app/test-pmd: fix rte_pci_tailq not initialized before used Yong Liu
2015-03-11 8:59 ` David Marchand
2015-03-11 17:26 ` David Marchand
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).