linux-kernel - Re: [patch 5/3] fastboot: sync the async execution before late

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 31 Jul 2008 20:56:01 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Simon Arlott <simon@...e.lp0.eu>
CC:	Alan Stern <stern@...land.harvard.edu>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu,
	Daniel Walker <dwalker@...sta.com>,
	USB list <linux-usb@...r.kernel.org>
Subject: Re: [patch 5/3] fastboot: sync the async execution before      late_initcall
 and move level 6s (sync) first

On 31-07-08 20:29, Simon Arlott wrote:

> Ok - so there could be some big improvements to be had by making the hcd 
> init happen as early as possible and the device initcalls later?

Arjan also needed a pre device_initcall() level for PCI core init now 
that the async device initcalls weren't governed just by link order 
anymore. He reused the device_initcall_sync() level, moving it to before 
device_initcall() itself (it used to be just behind).

Your above notion sounds like another good reason for inserting a real 
new level just before device_initcall(); if you move any of the device 
init to late initcall(), late_initcall() loses too much of its utility 
I'd feel (see start of this thread with various late_initcalls wanting 
to assume stuff).

Rene.
--
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/