From: Ingo Molnar <mingo@elte.hu>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: akpm@linux-foundation.org, jgarzik@pobox.com, muli@il.ibm.com,
davej@redhat.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, bunk@kernel.org, linux-bugs@dell.com,
linux-kernel@vger.kernel.org, greg@kroah.com,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH] fix x86 DMI checks for PCI quirks
Date: Fri, 2 May 2008 09:44:32 +0200 [thread overview]
Message-ID: <20080502074432.GA1372@elte.hu> (raw)
In-Reply-To: <20080502025427.GA23757@auslistsprd01.us.dell.com>
* Matt Domsch <Matt_Domsch@dell.com> wrote:
> fix x86 DMI checks for PCI quirks
>
> http://bugzilla.kernel.org/show_bug.cgi?id=10583
> https://bugzilla.redhat.com/show_bug.cgi?id=444791
>
> Since git commit 08f1c192c3c32797068bfe97738babb3295bbf42 (between
> kernels 2.6.22 and 2.6.23), arch/x86/pci/acpi.c has not called
> pcibios_scan_root(), which would have called
> arch/x86/pci/common.c:dmi_check_system(). This has prevented the
> quirks listed in pciprobe_dmi_table[] from being checked and
> appropriate action taken.
ugh ...
> This manifests itself in several Dell and HP servers not automatically
> having the pci=bfsort option be applied, as well as Samsung X20 and
> Compaq EVO N800c systems needing pci=assign-all-busses was no longer
> automatically applied.
>
> This patch moves the DMI tests into its own file, arch/x86/pci/dmi.c,
> and invokes them via subsys_initcall() before pci_acpi_init(),
> pci_legacy_init(), and pcibios_init() are called, which may rely upon
> these tests having been executed.
Jesse Barnes (new PCI maintainer) Cc:-ed.
i'm wondering how we could avoid such mishaps in the future. This was
broken from 2.6.23 through 2.6.25 - way too long. Perhaps we should
create a known signature of the device tree in user-space, and somehow
warn if the kernel changes it? Could this somehow be put into the
kernel?
Ingo
next prev parent reply other threads:[~2008-05-02 7:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 2:54 Matt Domsch
2008-05-01 11:23 ` Arjan van de Ven
2008-05-02 11:56 ` Matt Domsch
2008-05-02 7:44 ` Ingo Molnar [this message]
2008-05-02 9:19 ` Yinghai Lu
2008-05-02 13:56 ` Matt Domsch
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=20080502074432.GA1372@elte.hu \
--to=mingo@elte.hu \
--cc=Matt_Domsch@dell.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jgarzik@pobox.com \
--cc=linux-bugs@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=muli@il.ibm.com \
--cc=tglx@linutronix.de \
/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®