From: Arjan van de Ven <arjan@infradead.org>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
Pavel Machek <pavel@ucw.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Paul Diefenbaugh <paul.s.diefenbaugh@intel.com>,
Andy Grover <andrew.grover@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [patch 1/3] fastboot: Create a "asynchronous" initlevel
Date: Sun, 20 Jul 2008 08:35:30 -0700 [thread overview]
Message-ID: <20080720083530.1bc60ead@infradead.org> (raw)
In-Reply-To: <48834996.9060804@keyaccess.nl>
On Sun, 20 Jul 2008 16:20:06 +0200
Rene Herman <rene.herman@keyaccess.nl> wrote:
> On 20-07-08 13:10, Arjan van de Ven wrote:
>
> > On Sun, 20 Jul 2008 09:23:31 +0200
> > Rene Herman <rene.herman@keyaccess.nl> wrote:
> >
> >> Yes, I see. Unfortunately, WITH your patches, driver_probe_done()
> >> would also no longer be safe when run from a late_initcall() it
> >> would appear.
> >
> > true for now (but see below)
> >
> >> I have the sneaking suspicion that this is a bit of a fundamental
> >> issue. Turning some of the driver level (6) async basicaly removes
> >> the ordering between drivers and late_initcall (level 7).
> >
> > I was hoping to not need this ordering.
>
> May have found an issue with 3/3 for this same reason.
> > Thankfully it doesn't destroy it, the reason for this is that level
> > 6 itself tends to take long enough to get benefits. It's just that
> > if we can get both 6 and 7 it's nicer. But if we end up needing to
> > sync, so be it.
>
> I worry...
ok you convinced me... I'll post a followon patch that will have this
shortly once it finishes compiling/booting.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-07-20 15:35 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
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 [this message]
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=20080720083530.1bc60ead@infradead.org \
--to=arjan@infradead.org \
--cc=andrew.grover@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.s.diefenbaugh@intel.com \
--cc=pavel@ucw.cz \
--cc=rene.herman@keyaccess.nl \
--cc=rjw@sisk.pl \
/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