From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 9C3CF1B19E for ; Fri, 6 Oct 2017 01:21:43 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 15FCC20B75; Thu, 5 Oct 2017 19:21:43 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 05 Oct 2017 19:21:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=6/a+V1Utj/q2rlU Y0h2OpOjWPYRsJAeRjZzaA23waas=; b=ncVltq+jBjQTGVOyVPHUsp0fjf8l8ow RSeXtcG3dWU1eLHSztZjo1uJx2fskkDNtON7fzDhL4+Lr/+l7UCK1KdqakTc4JF4 ChA/Wk2q/6eBoVl3UMpv0BTusV37/YpvO8Cl6uWyTL7bqIAkExUt6jVP5kxNJDOB btpy6+iuf03s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=6/a+V1Utj/q2rlUY0h2OpOjWPYRsJAeRjZzaA23waas=; b=Xm7qBQEa CTTRI/Es5j1dkq9fpny565VV2hp15LcamkO73BDhX5uO14yCsy8FiIkYCMRCIoeT aQUI3dExIfwpWELOKrwAVnla5vtZ2/MslBh7D71sAAfdFwc6ddJDj/VvoPJz6q8I xgq3uSvpm3jeq1v94fHZH3GP6DsCzRLarGgtR44L9jyjbdllYszB6gnnvpIlrzJJ ntECOeQr/TPTB0G1Ubnl4SAzERtWFa+T+nakv8vmeZ7d44sURTq3DdxZKbMTR6SM 8MIhSCxBNauV3YYe5PcBNWOcJCgIg4xMBqO4tF6tF6u/jMgHWt2ckOv8Ca6+RGJJ +th+XUQwySXxKw== X-ME-Sender: X-Sasl-enc: ucoyx37QN7nJWFuI2nQ5bkYjRYJ/RkrbSZowYtEeAPH1 1507245702 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B47207FA70; Thu, 5 Oct 2017 19:21:42 -0400 (EDT) From: Thomas Monjalon To: Shreyansh Jain Cc: dev@dpdk.org, Jan Blunck , Hemant Agrawal Date: Fri, 06 Oct 2017 01:21:41 +0200 Message-ID: <2075457.Vvey9mxHue@xps> In-Reply-To: References: <20170812102220.27773-1-shreyansh.jain@nxp.com> <422ce0c6-7868-b601-2fe9-e361497d7b14@nxp.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] eal: bus scan and probe never fail 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, 05 Oct 2017 23:21:43 -0000 19/09/2017 20:51, Jan Blunck: > On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal wrote: > > Tested-by: Hemant Agrawal > > > > > > On 8/12/2017 3:52 PM, Shreyansh Jain wrote: > >> > >> Bus scan is responsible for finding devices over *all* buses. > >> Some of these buses might not be able to scan but that should > >> not prevent other buses to be scanned. > >> > > If scanning the bus fails this is signaling an error. In that case we > might even want to unregister the bus. A scan error seems important enough to be reported to the caller. OK to continue scanning other buses, but an error code should be returned. > >> Same is the case for probing. It is possible that some devices which > >> were scanned didn't have a specific driver. That should not prevent > >> other buses from being probed. > > Absolutely correct. Yes When we will have a probe notification, we will be able to notify the upper layer that a device probing has failed.