[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090114090433.45cf1e78@infradead.org>
Date: Wed, 14 Jan 2009 09:04:33 +0000
From: Arjan van de Ven <arjan@...radead.org>
To: Zhang Rui <rui.zhang@...el.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"mingo@...e.hu" <mingo@...e.hu>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH 1/6] fastboot: Asynchronous function calls to speed up
kernel boot
On Wed, 14 Jan 2009 13:32:43 +0800
Zhang Rui <rui.zhang@...el.com> wrote:
> > +
> > + wait_event(async_done, lowest_in_progress >= cookie);
> > +
>
> In some cases, we only want to wait for a specific cookie
> rather than all the cookies smaller than it.
>
> For example:
> device cookie
> ACPI battery 1
> ata port 0 2
> ata port 1 3
> ata port 0 and port 1 in the same host can not be probed in parallel.
>
> In this case, ata port1 should only wait for cookie 2 rather than
> both 1 and 2.
>
I really don't want to go this way; ordering is really important and I
don't want to break this.
If you really have a fully separate domain (and there's only few of
those in our kernel), then use a special run list.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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/
Powered by blists - more mailing lists