public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bzolnier@gmail.com, Matt Mackall <mpm@selenic.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH 3/6] lguest suppress IDE probing
Date: Wed, 06 Jun 2007 11:10:58 +1000	[thread overview]
Message-ID: <1181092258.14054.87.camel@localhost.localdomain> (raw)
In-Reply-To: <20070605170747.256f6631@the-village.bc.nu>

On Tue, 2007-06-05 at 17:07 +0100, Alan Cox wrote:
> On Wed, 06 Jun 2007 00:58:03 +1000
> Rusty Russell <rusty@rustcorp.com.au> wrote:
> 
> > The IDE probe is the slowest part of boot: by suppressing it we cut
> > boot from from 3 seconds to half a second.
> 
> NAK NAK NAK NAK NAK

Hi Alan!

> > AFAICT, the commandline is the easiest way to suppress the probing.
> 
> Gaa ... Rusty surely you have more taste than that.

Indeed, but it got attention 8)

> See include/asm-foo/ide.h
> 
> Add an lguest check to go with the pci check and for the lguest case just
> say "no controllers"

Actually, Jeremy suggested claiming the entire IO space.  That works for
Xen domU too, and makes some amount of sense.

> Better yet just don't compile in the old IDE stuff, lguest doesn't have a
> PCI or ISA bus anyway.

Sure, but the "run the same kernel as guest and host" is a really nice
feature.

> Alternatively make the IDE I/O space return 0xFF and it'll skip them
> anyway.

Hmm, every "in" should be returning 0xFFs, but I still get the delay and
the probing.  Xen domU gets it too.

Thanks!
Rusty.


  parent reply	other threads:[~2007-06-06  1:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 14:55 [PATCH 1/6] lguest example launcher fix Rusty Russell
2007-06-05 14:56 ` [PATCH 2/6] lguest tsc fix Rusty Russell
2007-06-05 14:58   ` [PATCH 3/6] lguest suppress IDE probing Rusty Russell
2007-06-05 15:00     ` [PATCH 4/6] lguest don't signal like crazy, use LHREQ_BREAK command Rusty Russell
2007-06-05 15:02       ` [PATCH 5/6] lguest use TSC Rusty Russell
2007-06-05 15:09         ` [PATCH 6/6] lguest use hrtimers Rusty Russell
2007-06-05 15:34       ` [PATCH 4/6] lguest don't signal like crazy, use LHREQ_BREAK command Matt Mackall
2007-06-06  0:07         ` Rusty Russell
2007-06-06  1:00           ` Matt Mackall
2007-06-05 15:32     ` [PATCH 3/6] lguest suppress IDE probing Matt Mackall
2007-06-05 16:07     ` Alan Cox
2007-06-05 16:10       ` Jeff Garzik
2007-06-05 17:09       ` James Morris
2007-06-06  1:10       ` Rusty Russell [this message]
2007-06-06 10:23         ` Alan Cox
2007-06-07  2:13           ` Rusty Russell
2007-06-07 14:45             ` Matt Mackall
2007-06-05 18:15   ` [PATCH 2/6] lguest tsc fix Andi Kleen
2007-06-06  0:25     ` Rusty Russell

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=1181092258.14054.87.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    /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