From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: linux-rdma@vger.kernel.org, linux-pci@vger.kernel.org,
dennis.dalessandro@intel.com, ira.weiny@intel.com
Subject: Re: [PATCH] [RFC] IB/hfi1: Fix port ordering issue in a multiport device
Date: Thu, 19 Jan 2017 08:51:22 -0800 [thread overview]
Message-ID: <7f728991-3bc6-b3ce-ebee-094a6439c369@intel.com> (raw)
In-Reply-To: <1484785071.2406.69.camel@redhat.com>
On 01/18/2017 04:17 PM, Doug Ledford wrote:
>>> EPROBE_DEFER is intended when waiting on other components the
>>> driver
>>> may need, not for setting stable names.
>> Also EPROBE_DEFER only works during boot time.
>> After boot when a module gets rmmod/insmod EPROBE_DEFER has no
>> effect.
> Are you positive about this? And even if you are, my answer is to fix
> the core to honor EPROBE_DEFER post boot.
Yes, the driver_deferred_probe_trigger() function is called from
late_initcall(). After boot there is nothing to call it again.
I'm investigating the udev path now as Jason suggested, but
udev has its own limitations.
I will see what it would take to extend the EPROBE_DEFER
functionality after boot.
Thanks,
--
Tadeusz
next prev parent reply other threads:[~2017-01-19 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 23:57 [PATCH] [RFC] IB/hfi1: Fix port ordering issue in a multiport device Tadeusz Struk
2017-01-11 7:12 ` Leon Romanovsky
2017-01-11 17:20 ` Tadeusz Struk
2017-01-11 17:59 ` Leon Romanovsky
2017-01-11 18:10 ` Jason Gunthorpe
[not found] ` <20170111181042.GC22783-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-01-18 21:01 ` Doug Ledford
[not found] ` <1484773260.2406.58.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-18 21:08 ` Jason Gunthorpe
2017-01-18 22:03 ` Tadeusz Struk
[not found] ` <934eb6c4-fbba-28d0-d6bb-f036cc9ced5c-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-01-19 0:17 ` Doug Ledford
2017-01-19 16:51 ` Tadeusz Struk [this message]
2017-01-19 0:16 ` Doug Ledford
[not found] ` <1484784989.2406.67.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-19 17:58 ` Jason Gunthorpe
2017-01-22 8:16 ` Leon Romanovsky
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=7f728991-3bc6-b3ce-ebee-094a6439c369@intel.com \
--to=tadeusz.struk@intel.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox