linux-kernel - Re: [PATCH 1/2] async: async device driver probing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 13 Feb 2014 15:59:59 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	吴章金 <falcon@...zu.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] async: async device driver probing

On Sun, Feb 09, 2014 at 08:40:43AM +0000, 吴章金 wrote:
> Hi, Greg
> 
> These two patches aim to thread the initcalls(only probes here) for SMP
> systems. to simplify the upgrade of Linux for Android smartphones, the modules
> are built into the Linux kernel image, and hence the initcalls are called in
> serial order, to speedup the booting, benefit from SMP, thread these initcalls
> may parallel the probings.
> 
> and I rechecked the deferred probing, seems it solves the problem of getting
> devices initialized in the right order, the probing will be threaded only if
> the probe fails with the -EPROBE_DEFER. it doesn't provide any mechanism to
> thread a probe explicitly.

It's up to the bus to do threaded probing, but watch out, that is almost
never the bottleneck in your boot process (hint, in Android, booting the
kernel is almost not even in the range that can be measured overall).
There are so many other things that Android does at boot time that could
be worked on instead of worrying about this :)

good luck,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/