All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Phil Endecott <phil_dubhl_endecott@chezphil.org>,
	linux-input <linux-input@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Slow boot due perhaps to locks in mouse and platform system
Date: Tue, 14 Oct 2008 11:37:09 -0400	[thread overview]
Message-ID: <20081014113709.5a2f2c2e@infradead.org> (raw)
In-Reply-To: <20081014112912.ZZRA012@mailhub.coreip.homeip.net>

On Tue, 14 Oct 2008 11:29:55 -0400
Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:

> On Tue, Oct 14, 2008 at 11:12:36AM -0400, Arjan van de Ven wrote:
> > On Tue, 14 Oct 2008 10:54:36 -0400
> > Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > > On Tue, Oct 14, 2008 at 03:19:28PM +0100, Phil Endecott wrote:
> > > > What can be done about this?  Is it unreasonable for the mouse
> > > > probing to take 2 seconds?  Should it not be holding the
> > > > conflicting lock while it is probing?  Does the platform
> > > > matching code really need to hold the lock when it's just
> > > > comparing the string names of the device and driver?
> > > >
> > 
> > the real thing is to not wait on this while booting;
> > my fastboot git tree has the patches to fix that part..
> > 
> 
> Could you please be more specific?

right now, the linux kernel boot will wait for this probing to be done
before mounting the root fs and then exec()ing /sbin/init.
On my test laptop this takes 7 seconds of .. nothing ;-)

the patch I have makes the kernel NOT wait for this, but just it tries
to mount root right away (and if that fails, it THEN waits and retries)

> 


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-10-14 15:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 14:19 Slow boot due perhaps to locks in mouse and platform system Phil Endecott
2008-10-14 14:54 ` Dmitry Torokhov
2008-10-14 15:12   ` Arjan van de Ven
2008-10-14 15:29     ` Dmitry Torokhov
2008-10-14 15:37       ` Arjan van de Ven [this message]
2008-10-14 23:17         ` Phil Endecott
2008-10-15  2:22           ` Arjan van de Ven
2008-10-15  9:19             ` Phil Endecott
2008-10-22 23:07               ` Phil Endecott
2008-10-14 15:37       ` Arjan van de Ven
2008-10-14 15:48         ` Dmitry Torokhov
2008-10-14 15:58           ` Arjan van de Ven
2008-10-14 16:18     ` Phil Endecott

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=20081014113709.5a2f2c2e@infradead.org \
    --to=arjan@infradead.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=phil_dubhl_endecott@chezphil.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.