From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 6D135695D for ; Thu, 23 Mar 2017 15:04:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490277876; x=1521813876; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=k6MJrnYz/yBbsr4usjmb7oTmmQMnMjOSSFO0Tm8ew3s=; b=QoPF14r10H53RaOi6R4b1roeta9FIHK0s4XTNWG3W5FmEQjhegr6b8L0 04TMIzXtvQYVIIHNPiCDKAg0SCZ7cw==; Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Mar 2017 07:04:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,210,1486454400"; d="scan'208";a="78593805" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.140]) by orsmga005.jf.intel.com with SMTP; 23 Mar 2017 07:04:32 -0700 Received: by (sSMTP sendmail emulation); Thu, 23 Mar 2017 14:04:31 +0000 Date: Thu, 23 Mar 2017 14:04:31 +0000 From: Bruce Richardson To: Aaron Conole Cc: dev@dpdk.org, Thomas Monjalon , Stephen Hemminger Message-ID: <20170323140431.GB8688@bricha3-MOBL3.ger.corp.intel.com> References: <20170322201940.24028-1-aconole@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170322201940.24028-1-aconole@redhat.com> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.8.0 (2017-02-23) Subject: Re: [dpdk-dev] [PATCH v7 00/14] 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2017 14:04:36 -0000 On Wed, Mar 22, 2017 at 04:19:26PM -0400, 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). > > Changes ->v2: > - Audited all "RTE_LOG (" calls that were introduced, and converted > to "RTE_LOG(" > - Added some fprintf(stderr, "") lines to indicate errors before logging > is initialized > - Removed assignments to errno. > - Changed patch 14/25 to reflect EFAULT, and document in 25/25 > > Changes ->v3: > - Checkpatch issues in patches 3 (spelling mistake), 9 (issue with leading > spaces), and 19 (braces around single line statement if-condition) > > Changes ->v4: > - Error text cleanup. > - Add a new check around rte_bus_scan(), added during the development of > this series. > > Changes ->v5: > - checkpatch.pl cleanup in patch 02/26 > - move rte_errno.h include from patch 15 to patch 02 > - remove stdbool.h and use int as return type in patch 06/26 > > Changes ->v6: > - convert all of the initialization calls to RTE_LOG() to rte_eal_init_alert() > - run through check-git-log and checkpatches > - add Bruce's ack to the series > > Changes ->v7: > - Squash a bunch of commits > - Make the corresponding BSD side changes > - refactor the PCI probe failure code to be more explicit in the intent > - Remove most of Bruce's acks (with all the shuffling/changes I think the > series should be re-evaluated) > Ran a sanity test compiling with clang on FreeBSD 11 and had a quick scan of the patches. All looks reasonably ok to me. Did not test on linux. Acked-by: Bruce Richardson