From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <aconole@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id 7DA721077
 for <dev@dpdk.org>; Tue, 14 Feb 2017 21:50:25 +0100 (CET)
Received: from int-mx13.intmail.prod.int.phx2.redhat.com
 (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id D65EE61BB9;
 Tue, 14 Feb 2017 20:50:25 +0000 (UTC)
Received: from dhcp-25-97.bos.redhat.com (dhcp-25-172.bos.redhat.com
 [10.18.25.172])
 by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 v1EKoOQu020528
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Tue, 14 Feb 2017 15:50:25 -0500
From: Aaron Conole <aconole@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
References: <20170208185142.28678-1-aconole@redhat.com>
 <20170209142953.8167-1-aconole@redhat.com>
 <20170209143814.595e74f5@xeon-e3>
Date: Tue, 14 Feb 2017 15:50:24 -0500
In-Reply-To: <20170209143814.595e74f5@xeon-e3> (Stephen Hemminger's message of
 "Thu, 9 Feb 2017 14:38:14 -0800")
Message-ID: <f7tr3308pkf.fsf@redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.5.110.39]); Tue, 14 Feb 2017 20:50:25 +0000 (UTC)
Subject: Re: [dpdk-dev] [PATCH v3 00/25] linux/eal: Remove most causes of
	panic on init
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 20:50:25 -0000

Stephen Hemminger <stephen@networkplumber.org> writes:

> On Thu,  9 Feb 2017 09:29:28 -0500
> Aaron Conole <aconole@redhat.com> 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