All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] driver core: add a debugfs entry to show deferred devices
Date: Sun, 8 Jul 2018 15:22:13 +0200	[thread overview]
Message-ID: <20180708132213.GA29000@kroah.com> (raw)
In-Reply-To: <20180708132107.GA25491@kroah.com>

On Sun, Jul 08, 2018 at 03:21:07PM +0200, Greg Kroah-Hartman wrote:
> On Sun, Jul 08, 2018 at 02:32:56AM +0200, Javier Martinez Canillas wrote:
> > With Device Trees (DT), the dependencies of the devices are defined in the
> > DT, then the drivers parse that information to lookup the needed resources
> > that have as dependencies.
> > 
> > Since drivers and devices are registered in a non-deterministic way, it is
> > possible that a device that is a dependency has not been registered yet by
> > the time that is looked up.
> > 
> > In this case the driver that requires this dependency cannot probe and has
> > to defer it. So the driver core adds it to a list of deferred devices that
> > is iterated again every time that a new driver is probed successfully.
> > 
> > For debugging purposes it may be useful to know what are the devices whose
> > probe function was deferred. Add a debugfs entry showing that information.
> > 
> >   $ cat /sys/kernel/debug/devices_deferred
> >   48070000.i2c:twl at 48:bci
> >   musb-hdrc.0.auto
> >   omapdrm.0
> > 
> > This information could be obtained partially by enabling debugging, but it
> > means that the kernel log has to be parsed and the probe deferral balanced
> > with the successes. This can be error probe and has to be done in a ad-hoc
> > manner by everyone who needs to debug these kind of issues.
> > 
> > Since the information is already known by the kernel, just show it to make
> > it easier to debug.
> > 
> > Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> > Reviewed-by: Mark Brown <broonie@kernel.org>
> > 
> > ---
> > 
> > Changes since RFC v1:
> > - Remove unneeded ret variable from deferred_devs_show()
> > 
> > Changes since RFC v2:
> > - Use DEFINE_SHOW_ATTRIBUTE() macro.
> > - Don't propagate debugfs_create_file() error.
> > - Remove IS_ENABLED(CONFIG_DEBUG_FS) guards.
> > - Drop RFC prefix.
> > 
> > Changes since v1:
> > - Better explain in the commit message why this patch is useful.
> > - Rename deferred_devices entry to devices_deferred.
> > - Add an exit function and remove the debugfs entry.
> > 
> > Changes since v2:
> > - Add Andy Shevchenko and Mark Brown Reviewed-by tag.
> > - Rebase on top of Greg's driver-core-next branch.
> > 
> > 
> >  drivers/base/dd.c | 30 ++++++++++++++++++++++++++++++
> >  1 file changed, 30 insertions(+)
> > 
> > diff --git a/drivers/base/dd.c b/drivers/base/dd.c
> > index 6ea9c5cece7..140f534ee9c 100644
> > --- a/drivers/base/dd.c
> > +++ b/drivers/base/dd.c
> > @@ -16,6 +16,7 @@
> >   * Copyright (c) 2007-2009 Novell Inc.
> >   */
> >  
> > +#include <linux/debugfs.h>
> >  #include <linux/device.h>
> >  #include <linux/delay.h>
> >  #include <linux/dma-mapping.h>
> > @@ -53,6 +54,8 @@ static DEFINE_MUTEX(deferred_probe_mutex);
> >  static LIST_HEAD(deferred_probe_pending_list);
> >  static LIST_HEAD(deferred_probe_active_list);
> >  static atomic_t deferred_trigger_count = ATOMIC_INIT(0);
> > +static struct dentry *deferred_devices;
> > +static bool initcalls_done;
> 
> Wait, why add this variable?  No one uses it that I can see in this
> patch, doesn't it create a build warning?
> 
> You did test-build this, right?

I just tested it, it causes a build warning, which implies that you did
not test this :(

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>,
	Rob Herring <robh@kernel.org>, Mark Brown <broonie@kernel.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] driver core: add a debugfs entry to show deferred devices
Date: Sun, 8 Jul 2018 15:22:13 +0200	[thread overview]
Message-ID: <20180708132213.GA29000@kroah.com> (raw)
In-Reply-To: <20180708132107.GA25491@kroah.com>

On Sun, Jul 08, 2018 at 03:21:07PM +0200, Greg Kroah-Hartman wrote:
> On Sun, Jul 08, 2018 at 02:32:56AM +0200, Javier Martinez Canillas wrote:
> > With Device Trees (DT), the dependencies of the devices are defined in the
> > DT, then the drivers parse that information to lookup the needed resources
> > that have as dependencies.
> > 
> > Since drivers and devices are registered in a non-deterministic way, it is
> > possible that a device that is a dependency has not been registered yet by
> > the time that is looked up.
> > 
> > In this case the driver that requires this dependency cannot probe and has
> > to defer it. So the driver core adds it to a list of deferred devices that
> > is iterated again every time that a new driver is probed successfully.
> > 
> > For debugging purposes it may be useful to know what are the devices whose
> > probe function was deferred. Add a debugfs entry showing that information.
> > 
> >   $ cat /sys/kernel/debug/devices_deferred
> >   48070000.i2c:twl@48:bci
> >   musb-hdrc.0.auto
> >   omapdrm.0
> > 
> > This information could be obtained partially by enabling debugging, but it
> > means that the kernel log has to be parsed and the probe deferral balanced
> > with the successes. This can be error probe and has to be done in a ad-hoc
> > manner by everyone who needs to debug these kind of issues.
> > 
> > Since the information is already known by the kernel, just show it to make
> > it easier to debug.
> > 
> > Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> > Reviewed-by: Mark Brown <broonie@kernel.org>
> > 
> > ---
> > 
> > Changes since RFC v1:
> > - Remove unneeded ret variable from deferred_devs_show()
> > 
> > Changes since RFC v2:
> > - Use DEFINE_SHOW_ATTRIBUTE() macro.
> > - Don't propagate debugfs_create_file() error.
> > - Remove IS_ENABLED(CONFIG_DEBUG_FS) guards.
> > - Drop RFC prefix.
> > 
> > Changes since v1:
> > - Better explain in the commit message why this patch is useful.
> > - Rename deferred_devices entry to devices_deferred.
> > - Add an exit function and remove the debugfs entry.
> > 
> > Changes since v2:
> > - Add Andy Shevchenko and Mark Brown Reviewed-by tag.
> > - Rebase on top of Greg's driver-core-next branch.
> > 
> > 
> >  drivers/base/dd.c | 30 ++++++++++++++++++++++++++++++
> >  1 file changed, 30 insertions(+)
> > 
> > diff --git a/drivers/base/dd.c b/drivers/base/dd.c
> > index 6ea9c5cece7..140f534ee9c 100644
> > --- a/drivers/base/dd.c
> > +++ b/drivers/base/dd.c
> > @@ -16,6 +16,7 @@
> >   * Copyright (c) 2007-2009 Novell Inc.
> >   */
> >  
> > +#include <linux/debugfs.h>
> >  #include <linux/device.h>
> >  #include <linux/delay.h>
> >  #include <linux/dma-mapping.h>
> > @@ -53,6 +54,8 @@ static DEFINE_MUTEX(deferred_probe_mutex);
> >  static LIST_HEAD(deferred_probe_pending_list);
> >  static LIST_HEAD(deferred_probe_active_list);
> >  static atomic_t deferred_trigger_count = ATOMIC_INIT(0);
> > +static struct dentry *deferred_devices;
> > +static bool initcalls_done;
> 
> Wait, why add this variable?  No one uses it that I can see in this
> patch, doesn't it create a build warning?
> 
> You did test-build this, right?

I just tested it, it causes a build warning, which implies that you did
not test this :(

greg k-h

  reply	other threads:[~2018-07-08 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-08  0:32 [PATCH v3] driver core: add a debugfs entry to show deferred devices Javier Martinez Canillas
2018-07-08  0:32 ` Javier Martinez Canillas
2018-07-08 13:21 ` Greg Kroah-Hartman
2018-07-08 13:21   ` Greg Kroah-Hartman
2018-07-08 13:22   ` Greg Kroah-Hartman [this message]
2018-07-08 13:22     ` Greg Kroah-Hartman
2018-07-08 13:33     ` Javier Martinez Canillas
2018-07-08 13:33       ` Javier Martinez Canillas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180708132213.GA29000@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.