public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Matthew Wilcox <matthew@wil.cx>, Andi Kleen <ak@suse.de>,
	Jeff Chua <jeff.chua.linux@gmail.com>,
	Aaron Durbin <adurbin@google.com>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	gregkh@suse.de, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3)
Date: Wed, 8 Nov 2006 18:26:50 +0100	[thread overview]
Message-ID: <20061108172650.GC4729@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0611080803280.3667@g5.osdl.org>

On Wed, Nov 08, 2006 at 08:05:18AM -0800, Linus Torvalds wrote:
> 
> 
> On Wed, 8 Nov 2006, Matthew Wilcox wrote:
> >
> > On Wed, Nov 08, 2006 at 08:39:44AM +0100, Andi Kleen wrote:
> > > ACPI knows the number of busses.
> > 
> > But what if the number of busses increases later, eg by hotplugging
> > a card with a PCI-PCI bridge on it?  Or does it know the number of
> > busses which can be supported by this machine's MMCONFIG region?
> 
> ACPI will give the maximum number.
> 
> However, in this case, the correct thing to do (always _has_ been) is to 
> not use ACPI for _anything_, but just read the base and the size of the 
> MMCONFIG region from the hardware itself.
> 
> Anyway, I do not consider this a regression. MMCONFIG has _never_ worked 
> reliably. It has always been a case of "we can make it work on some 
> machines by making it break on others".

It is a serious regression:

The problem is that with the default CONFIG_PCI_GOANY, MMCONFIG is the 
_first_ method tried.

In practice, this implies that nearly every system possibly affected 
will suffer from a MMCONFIG breakage like the one Jeff observed...

> 			Linus

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


       reply	other threads:[~2006-11-08 17:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0611080056480.12828@silvia.corp.fedex.com>
     [not found] ` <20061107171143.GU27140@parisc-linux.org>
     [not found]   ` <200611080839.46670.ak@suse.de>
     [not found]     ` <20061108122237.GF27140@parisc-linux.org>
     [not found]       ` <Pine.LNX.4.64.0611080803280.3667@g5.osdl.org>
2006-11-08 17:26         ` Adrian Bunk [this message]
2006-11-08 17:49           ` [discuss] Re: 2.6.19-rc4: known unfixed regressions (v3) Linus Torvalds
2006-11-08 18:08             ` Linus Torvalds
2006-11-08 18:36               ` Linus Torvalds
2006-11-10  6:25                 ` Jeff Chua
2006-11-10  6:43                   ` Andrew Morton
2006-11-10  9:21                     ` Jeff Chua
2006-11-10  6:56               ` Andi Kleen
2006-11-10 10:16                 ` Alan Cox
2006-11-10 14:02                   ` Jeff Garzik
2006-11-10 13:56               ` Jeff Garzik
2006-11-08 18:17             ` Aaron Durbin
2006-11-10  5:53 Jeff Chua

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=20061108172650.GC4729@stusta.de \
    --to=bunk@stusta.de \
    --cc=adurbin@google.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    --cc=torvalds@osdl.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