From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
linux-ide@vger.kernel.org
Subject: Re: [patch 1/2] fastboot: Add a module parameter to skip probing of specific ports
Date: Tue, 12 Aug 2008 08:39:03 +0100 [thread overview]
Message-ID: <20080812083903.6d402c2e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20080811153641.706726ec@infradead.org>
On Mon, 11 Aug 2008 15:36:41 -0700
Arjan van de Ven <arjan@infradead.org> wrote:
>
> From: Kristen Accardi <kristen.c.accardi@intel.com>
> Subject: [PATCH] libata: Add a module parameter to skip probing of specific ports
>
> Port probing by libata can easily take 10% or more of the kernel boot
> time (2%+ of total). For cases where one knows there is nothing
> connected to certain ports (for example on netbooks) this is a waste
> of boot time.
>
> This patch adds a module parameter that allows the admin to specify
> to skip ports (specified by a bitmask) and recoup this boot time.
> This capability is potentially also useful to get systems to boot
> for cases where port-probing on a certain ports causes crashes.
>
> A follow-on patch will add the capability to use DMI identification
> to automate this for certain known systems.
What happens if I plug in an additional libata using device ? What
defines the probe order here particularly as people are pushing for
parallel probing of multiple devices.
This doesn't appear to make any rational sense as the mask isn't tied to
the actual bus device identifier to keep it on the same port. It might
kidn of work for an EEEPC (until you see what people retrofit into the
corners of them) but it isn't a valid general solution.
Also the EEE problem seems to be a controller specific screwup - they
didn't apparently manage the enablebits on the ATA controller correctly,
so it belongs in that driver. That also lets you tie it to the right
system, pci id, bus id so it'll always hit the right device.
(Plus double check the enables code in case you are papering over the
real bug)
Second problem is you've changed the API. Several drivers do things on
the port 0 register they know they will receive and will simply crash and
burn if you change this.
NAK this patch for now: right theory, wrong implementation. Please post a
version which uses DMI in the relevant driver and checks the PCI DEVFN
matches.
next prev parent reply other threads:[~2008-08-12 7:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 22:35 [patch 0/2] fastboot: allow skipping probing of known-unused ports in libata Arjan van de Ven
2008-08-11 22:36 ` [patch 1/2] fastboot: Add a module parameter to skip probing of specific ports Arjan van de Ven
2008-08-12 7:39 ` Alan Cox [this message]
2008-08-12 11:36 ` Arjan van de Ven
2008-08-12 12:00 ` Alan Cox
2008-08-12 14:02 ` Arjan van de Ven
2008-08-12 14:21 ` Alan Cox
2008-08-11 22:37 ` [patch 2/2] fastboot: use a DMI match table to set defaults for port-disable Arjan van de Ven
2008-08-12 1:09 ` Marcel Holtmann
2008-08-12 5:04 ` Arjan van de Ven
2008-08-12 8:10 ` Alan Cox
2008-08-12 11:37 ` Arjan van de Ven
2008-08-12 11:58 ` Alan Cox
2008-08-20 22:46 ` Bjorn Helgaas
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=20080812083903.6d402c2e@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®