public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	bzolnier@gmail.com, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH 3/6] lguest suppress IDE probing
Date: Thu, 7 Jun 2007 09:45:08 -0500	[thread overview]
Message-ID: <20070607144508.GV11115@waste.org> (raw)
In-Reply-To: <1181182387.14054.157.camel@localhost.localdomain>

On Thu, Jun 07, 2007 at 12:13:07PM +1000, Rusty Russell wrote:
> On Wed, 2007-06-06 at 11:23 +0100, Alan Cox wrote:
> > > > 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.
> > 
> > Modules dear boy, modules ;)
> 
> For some reason, pulling half the kernel's brains out into a separately
> maintained userspace seems to make things less reliable.  I always build
> in everything I need to boot.
> 
> Perhaps this makes me an old-timer.
> 
> > > > 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.
> > 
> > Can you see in a debugger where it is spending the time. 0xFF should be
> > taken as "no port, move on nothing to see"
> 
> Well, the code is a little opaque to me, but do_probe() calls msleep(50)
> three times.  According to gdb this gets called 27 times -> 4.05
> seconds.

Yep. libata somehow manages to avoid most of these, it'd be
interesting to work out why.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-06-07 14:45 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
2007-06-06 10:23         ` Alan Cox
2007-06-07  2:13           ` Rusty Russell
2007-06-07 14:45             ` Matt Mackall [this message]
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=20070607144508.GV11115@waste.org \
    --to=mpm@selenic.com \
    --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=rusty@rustcorp.com.au \
    /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