From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: parse args before any kinds of init Date: Wed, 07 May 2014 15:06:08 +0200 Message-ID: <1851834.kBMPGP7GOf@xps13> References: <534CA193.2000604@gmail.com> <2073730.rjlHe4Kf7A@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Wang Sheng-Hui Return-path: In-Reply-To: <2073730.rjlHe4Kf7A@xps13> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2014-05-05 17:50, Thomas Monjalon: > 2014-04-15 11:03, Wang Sheng-Hui: > > Parse args first, to resolve any invalid args and give out the usage > > string. E.g './helloworld --invalid', the '--invalid' will be checked > > before any init. After the options are checked, take any init actions. > > > > Signed-off-by: Wang Sheng-Hui > > [...] > > @@ -964,16 +969,16 @@ rte_eal_init(int argc, char **argv) > > > > thread_id = pthread_self(); > > > > + fctret = eal_parse_args(argc, argv); > > + if (fctret < 0) > > + exit(1); > > + > > > > if (rte_eal_log_early_init() < 0) > > > > rte_panic("Cannot init early logs\n"); > > > > if (rte_eal_cpu_init() < 0) > > > > rte_panic("Cannot detect lcores\n"); > > > > - fctret = eal_parse_args(argc, argv); > > - if (fctret < 0) > > - exit(1); > > - > > You should move eal_parse_args() just after rte_eal_log_early_init() in > order to have logs available. When double checking, I saw this commit which justify why rte_eal_cpu_init() is before eal_parse_args(): http://dpdk.org/browse/dpdk/commit/?id=f563a3727b5dba If the goal is to move debug lines in cpu_init, you should split rte_eal_log_early_init() in 2 functions: 1 to detect cores and 1 for debug summary. By the way, these are debug logs which should be disabled by default. -- Thomas