mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: ning.a.zhang@intel.com
Cc: gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com,
	linux-kernel@vger.kernel.org, mark.gross@intel.com
Subject: Re: [PATCH] driver core: support bus manage deferred probe
Date: Wed, 18 Jul 2018 17:16:47 +0000	[thread overview]
Message-ID: <20180718171647.xa3nyhvlwwejht7l@penguin> (raw)
In-Reply-To: <20180629070226.24506-1-ning.a.zhang@intel.com>

Hi,

On Fri, Jun 29, 2018 at 03:02:26PM +0800, ning.a.zhang@intel.com wrote:
> From: Zhang Ning <ning.a.zhang@intel.com>
> 
> deferred probe will be hanlded by deferred_probe_initcall,
> starts at late_initcall.
> 
> this is too late to handle deferred probe, this will block kernel exec
> to userspace, make kernel initial time longer.
> 
> if we know when required resources are ready for a list of devices,
> related deferred drivers can be probe earlier.
> 
> add these kinds of drivers into logical list,
> eg, bus_type->deferred_probe_pending_list,
> then it can be easily handled by bus driver.

I do not see why bus driver would have a better knowledge about its
device dependencies to accelerate deferred probe retries; it all depends
on the platform. On some platform PCI is essential and devices on PCI
bus are needed early, on others we can push PCI initialization to the
very end as there only a couple devices hanging off PCI bus.

You need to find a better way to decide when to reprobe a device, and
that requires analyzing and tracking the dependencies between devices.

Thanks.

-- 
Dmitry

      parent reply	other threads:[~2018-07-18 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29  7:02 ning.a.zhang
2018-06-29 10:56 ` kbuild test robot
2018-07-18 17:16 ` Dmitry Torokhov [this message]

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=20180718171647.xa3nyhvlwwejht7l@penguin \
    --to=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.gross@intel.com \
    --cc=ning.a.zhang@intel.com \
    --cc=rafael.j.wysocki@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®