[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0906241615160.18460@localhost.localdomain>
Date: Wed, 24 Jun 2009 16:21:09 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Yinghai Lu <yinghai@...nel.org>
cc: Ingo Molnar <mingo@...e.hu>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Gary Hade <garyhade@...ibm.com>,
Matthew Wilcox <matthew@....cx>,
Larry Finger <Larry.Finger@...inger.net>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-pci@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jaswinder Singh Rajput <jaswinder@...nel.org>
Subject: Re: [PATCH] x86/pci: don't use crs for root if we only have one root
bus
On Wed, 24 Jun 2009, Linus Torvalds wrote:
>
> I'm happy to apply various patches to fix it up, but regardless, I thinkwe
> should revert that commit as bogus. We can try making it the default again
> next round, when maybe it will be true that it doesn't cause issues.
Btw, I really think our _CRS handling sucks.
There's two things that you can do with _CRS:
- use the _existence_ of it as an indicator of a root bus
- try to use it to populate the resource tree.
And quite frankly, I think #2 is broken. There's no way in hell that ACPI
tables are ever going to be better than just asking the hardware. We've
gone through this before. Trusting ACPI over the hardware is just
FUNDAMENTALLY WRONG.
So I'm just going to do that revert. I'm not sure if it ever makes sense
to make that insane _CRS code the default. It seems like a fundamentally
flawed idea.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists