From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Conole Subject: Re: [PATCH v3 00/25] linux/eal: Remove most causes of panic on init Date: Tue, 14 Feb 2017 15:50:24 -0500 Message-ID: References: <20170208185142.28678-1-aconole@redhat.com> <20170209142953.8167-1-aconole@redhat.com> <20170209143814.595e74f5@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain Cc: dev@dpdk.org, Bruce Richardson To: Stephen Hemminger Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 7DA721077 for ; Tue, 14 Feb 2017 21:50:25 +0100 (CET) In-Reply-To: <20170209143814.595e74f5@xeon-e3> (Stephen Hemminger's message of "Thu, 9 Feb 2017 14:38:14 -0800") List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Stephen Hemminger writes: > On Thu, 9 Feb 2017 09:29:28 -0500 > Aaron Conole wrote: > >> In many cases, it's enough to simply let the application know that the >> call to initialize DPDK has failed. A complete halt can then be >> decided by the application based on error returned (and the app could >> even attempt a possible re-attempt after some corrective action by the >> user or application). >> >> ... >> > > I worry that some of these early failure messages may never be visible > because the logging system has not been initialized. Might be safer to > just use fprintf(stderr, ...) or define a new wrapper function. Thanks for the suggestion, Stephen! I've folded it into my series. -Aaron