[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0906241607100.18460@localhost.localdomain>
Date: Wed, 24 Jun 2009 16:09:36 -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
Should we not just revert 9e9f46c44e487af0a82eb61b624553e2f7118f5b?
The thing says:
"At this point, it seems to solve more problems than it causes, so let's
try using it by default. It's an easy revert if it ends up causing
trouble."
and it clearly does _not_ solve more problems than it causes, and the
whole message in that commit implies we should revert it.
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.
What did it even ever help with?
Linus
On Wed, 24 Jun 2009, Yinghai Lu wrote:
>
> for AMD system, when only one PCI root, just set PCI_NO_ROOT_CRS for it
>
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>
> ---
> arch/x86/pci/amd_bus.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> Index: linux-2.6/arch/x86/pci/amd_bus.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/pci/amd_bus.c
> +++ linux-2.6/arch/x86/pci/amd_bus.c
> @@ -561,6 +561,10 @@ static int __init early_fill_mp_bus_info
> }
> }
>
> + /* don't use _CRS if we only have one root */
> + if (pci_root_num <= 1)
> + pci_probe |= PCI_NO_ROOT_CRS;
> +
> return 0;
> }
>
>
--
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