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 > > > >
