From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <anatoly.burakov@intel.com>
Received: from mga03.intel.com (mga03.intel.com [143.182.124.21])
 by dpdk.org (Postfix) with ESMTP id A0A87B0AB
 for <dev@dpdk.org>; Wed, 18 Jun 2014 12:26:17 +0200 (CEST)
Received: from azsmga001.ch.intel.com ([10.2.17.19])
 by azsmga101.ch.intel.com with ESMTP; 18 Jun 2014 03:26:32 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.01,499,1400050800"; d="scan'208";a="446959769"
Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159])
 by azsmga001.ch.intel.com with ESMTP; 18 Jun 2014 03:26:09 -0700
Received: from irsmsx101.ger.corp.intel.com ([169.254.1.245]) by
 IRSMSX104.ger.corp.intel.com ([169.254.5.136]) with mapi id 14.03.0123.003;
 Wed, 18 Jun 2014 11:26:08 +0100
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>, Thomas Monjalon
 <thomas.monjalon@6wind.com>
Thread-Topic: [dpdk-dev] [PATCH] vfio: open VFIO container at startup rather
 than during init
Thread-Index: AQHPikzmqXPLJ58Ywk2jfElMWsSSHZt2kG4AgAAUuLCAAAUHwA==
Date: Wed, 18 Jun 2014 10:26:08 +0000
Message-ID: <C6ECDF3AB251BE4894318F4E451236976CC9CCAC@IRSMSX101.ger.corp.intel.com>
References: <4bf447650cc99e316e6427e3a1c134dd417af4ec.1402996488.git.anatoly.burakov@intel.com>
 <5481188.YHqy5HFYGY@xps13>
 <C6ECDF3AB251BE4894318F4E451236976CC9CB58@IRSMSX101.ger.corp.intel.com>
 <3EB4FA525960D640B5BDFFD6A3D891261B1C6009@IRSMSX102.ger.corp.intel.com>
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891261B1C6009@IRSMSX102.ger.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.181]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] vfio: open VFIO container at startup rather
 than during init
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <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: Wed, 18 Jun 2014 10:26:18 -0000

Hi Cristian,

> I would suggest we add a log message explaining which mechanism is loaded
> (igb_uio/vfio) and why (e.g. tried vfio first but container could not be
> opened, so falling back to igb_uio, etc).

This already happens.

If the container could not be loaded for whatever reason, the log message i=
s displayed (it did before, but the previous code didn't account for situat=
ions such as Bruce was having, hence the patch). If VFIO is loaded and enab=
led, all drivers will then report either being bound or skipped (e.g. "not =
bound to VFIO, skipping").

Best regards,
Anatoly Burakov
DPDK SW Engineer