From: Greg KH <gregkh@suse.de>
To: tcamuso@redhat.com
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
prarit@redhat.com
Subject: Re: [PATCH 0/5]PCI: x86 MMCONFIG
Date: Wed, 19 Dec 2007 15:16:09 -0800 [thread overview]
Message-ID: <20071219231609.GE24219@suse.de> (raw)
In-Reply-To: <20071219221746.20362.39243.sendpatchset@dhcp83-188.boston.redhat.com>
On Wed, Dec 19, 2007 at 05:17:46PM -0500, tcamuso@redhat.com wrote:
> OVERVIEW
> =======
>
> The patches should be applied in sequence to obviate any
> possible build problems.
>
> The patch-set was built against 2.6.24-rc5
>
> Description
> ===========
>
> There exist devices that do not respond correctly to PCI
> MMCONFIG accesses in x86 platforms.
What devices are these? Do you have reports of them somewhere?
> This patch-set detects the problem by comparing an MMCONFIG
> read to a Legacy PCI config read of the vendor/device dword
> of every device discovered during the PCI probing sequence.
>
> A miscompare means that a device does not correctly respond
> to MMCONFIG accesses. When the patch code detects this condition,
> the bus that serves this device, and all subordinate buses, will
> be programmed to use Legacy PCI Config accesses.
>
> This patch-set DOES NOT detect devices that generate machine
> checks against MMCONFIG accesses. For such systems,
> "pci=nommconf" is required in the boot command.
That sounds like this patchset can cause bad side affects on hardware
that currently works just fine. That is not a good thing to be adding
to the kernel, right?
thanks,
greg k-h
next prev parent reply other threads:[~2007-12-19 23:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071219221746.20362.39243.sendpatchset@dhcp83-188.boston.redhat.com>
[not found] ` <20071219221751.20362.23451.sendpatchset@dhcp83-188.boston.redhat.com>
2007-12-19 23:04 ` [PATCH 1/5]PCI: x86 MMCONFIG: introduce PCI_USING_MMCONF Greg KH
[not found] ` <4769B035.9020005@redhat.com>
[not found] ` <20071220001936.GA23791@suse.de>
2007-12-20 0:49 ` Tony Camuso
[not found] ` <20071219221756.20362.84805.sendpatchset@dhcp83-188.boston.redhat.com>
2007-12-19 23:06 ` [PATCH 2/5]PCI: x86 MMCONFIG: add legacy pci conf functions Greg KH
[not found] ` <20071219221806.20362.25964.sendpatchset@dhcp83-188.boston.redhat.com>
2007-12-19 23:10 ` [PATCH 4/5]PCI: x86 MMCONFIG: introduce pcibios_fix_bus_scan() Greg KH
2007-12-19 23:14 ` Greg KH
2007-12-19 23:16 ` Greg KH [this message]
[not found] <fa.zIbPFbLub6ANMT5vMxS6hx+dfv0@ifi.uio.no>
[not found] ` <fa.3T2SqNjavN55hanLOjr3RO+WalE@ifi.uio.no>
2007-12-20 0:12 ` [PATCH 0/5]PCI: x86 MMCONFIG Robert Hancock
2007-12-20 12:28 [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG] Tony Camuso
2007-12-20 17:22 ` Greg KH
2007-12-20 18:25 ` Tony Camuso
2007-12-20 21:57 ` Greg KH
2007-12-20 22:36 ` Tony Camuso
2007-12-20 22:40 ` Greg KH
2008-01-08 3:20 ` [PATCH 0/5]PCI: x86 MMCONFIG Tony Camuso
2008-01-08 4:56 ` Greg KH
2008-01-08 13:14 ` Tony Camuso
2008-01-08 13:36 ` Greg KH
2008-01-08 13:44 ` Tony Camuso
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=20071219231609.GE24219@suse.de \
--to=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=prarit@redhat.com \
--cc=tcamuso@redhat.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;
as well as URLs for NNTP newsgroup(s).