From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Horman Subject: Re: [PATCH] vfio: open VFIO container at startup rather than during init Date: Wed, 18 Jun 2014 07:00:18 -0400 Message-ID: <20140618110018.GA7587@hmsreliant.think-freely.org> References: <4bf447650cc99e316e6427e3a1c134dd417af4ec.1402996488.git.anatoly.burakov@intel.com> <5481188.YHqy5HFYGY@xps13> <3EB4FA525960D640B5BDFFD6A3D891261B1C6009@IRSMSX102.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Burakov, Anatoly" Return-path: Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Wed, Jun 18, 2014 at 10:26:08AM +0000, Burakov, Anatoly wrote: > 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 is displayed (it did before, but the previous code didn't account for situations such as Bruce was having, hence the patch). If VFIO is loaded and enabled, all drivers will then report either being bound or skipped (e.g. "not bound to VFIO, skipping"). I think what Thomas wants is for you to resend the patch with a proper changelog entry added to it, so the commit has an explination of what was changed and, for posterity. Neil > > Best regards, > Anatoly Burakov > DPDK SW Engineer > > > >