From: Rene Herman <rene.herman@keyaccess.nl>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [patch 1/3] fastboot: Create a "asynchronous" initlevel
Date: Sat, 19 Jul 2008 10:10:09 +0200 [thread overview]
Message-ID: <4881A161.7050902@keyaccess.nl> (raw)
In-Reply-To: <48819D92.8050904@keyaccess.nl>
On 19-07-08 09:53, Rene Herman wrote:
> On 19-07-08 00:16, Arjan van de Ven wrote:
>
>> +static void __init do_initcalls(void)
>> +{
>> + initcall_t *call;
>> + static DECLARE_WORK(async_work, do_async_initcalls);
>> + int phase = 0; /* 0 = levels 0 - 6, 1 = level 6a, 2 = after level
>> 6a */
>> +
>> + async_init_wq = create_singlethread_workqueue("kasyncinit");
>> +
>> + for (call = __initcall_start; call < __initcall_end; call++) {
>> + if (phase == 0 && call >= __async_initcall_start) {
>> + phase = 1;
>> + queue_work(async_init_wq, &async_work);
>> + }
>> + if (phase == 1 && call >= __async_initcall_end)
>> + phase = 2;
>> + if (phase != 1)
>> + do_one_initcall(*call);
>> + }
>
> I'm not sure about this comment, being not very sure about the semantics
> of late_initcall but shouldn't late_initcall (level 7) wait for 6s to
> have completed?
Following up on this myself -- see for example kernel/power/disk.c:
power_suspend(). It's a late intitcall so that, as it comments, "all
devices are discovered and initialized". However, your first followup
patch makes the USB HCI init async meaning that any USB storage device
might not be ready yet when it runs, no?
Rene.
next prev parent reply other threads:[~2008-07-19 8:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 22:15 [patch 0/3] fastboot patches series 1 Arjan van de Ven
2008-07-18 22:16 ` [patch 1/3] fastboot: Create a "asynchronous" initlevel Arjan van de Ven
2008-07-19 1:22 ` Daniel Walker
2008-07-19 3:44 ` Arjan van de Ven
2008-07-19 4:11 ` Daniel Walker
2008-07-19 4:58 ` Arjan van de Ven
2008-07-19 5:20 ` Arjan van de Ven
2008-07-19 15:24 ` Daniel Walker
2008-07-19 15:35 ` Arjan van de Ven
2008-07-19 16:08 ` Daniel Walker
2008-07-19 16:14 ` Arjan van de Ven
2008-07-19 4:28 ` Daniel Walker
2008-07-19 7:53 ` Rene Herman
2008-07-19 8:10 ` Rene Herman [this message]
2008-07-19 15:44 ` Arjan van de Ven
2008-07-20 7:23 ` Rene Herman
2008-07-20 11:10 ` Arjan van de Ven
2008-07-20 14:20 ` Rene Herman
2008-07-20 15:35 ` Arjan van de Ven
2008-07-18 22:16 ` [patch 2/3] fastboot: turn the USB hostcontroller initcalls into async initcalls Arjan van de Ven
2008-07-18 22:17 ` [patch 3/3] fastboot: convert a few non-critical ACPI drivers to " Arjan van de Ven
2008-07-19 4:51 ` [patch 0/3] fastboot patches series 1 Simon Arlott
2008-07-19 5:16 ` Arjan van de Ven
2008-07-19 5:47 ` Simon Arlott
2008-07-19 10:22 ` Andi Kleen
2008-07-20 8:31 ` Ingo Molnar
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=4881A161.7050902@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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