From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org, Gary Hade <garyhade@us.ibm.com>,
Alex Chiang <achiang@hp.com>,
linux-acpi@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: [PATCH] x86/pci: do assign root bus res if _CRS is used
Date: Mon, 27 Apr 2009 13:15:33 -0700 [thread overview]
Message-ID: <49F61265.10201@kernel.org> (raw)
In-Reply-To: <200904271344.04099.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> On Monday 20 April 2009 07:35:40 pm Yinghai Lu wrote:
>> it wil be overwriten later if _CRS is used, so don't bother to set it.
>>
>> [ Impact: cleanup ]
>>
>> Signed-off-by: Yinghai Lu <yinghai@kernel.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
>> @@ -100,6 +100,10 @@ void x86_pci_root_bus_res_quirks(struct
>> int j;
>> struct pci_root_info *info;
>>
>> + /* don't go for it if _CRS is used */
>> + if (pci_probe & PCI_USE__CRS)
>> + return;
>> +
>> /* if only one root bus, don't need to anything */
>> if (pci_root_num < 2)
>> return;
>
> This isn't a comment on this patch per se.
>
> I am concerned about the fact that "pci=use_crs" is not the default.
> From the changelog of 62f420f8282, it sounds like you have to boot an
> IBM x3850 with "pci=use_crs" to make hot-plug work, even though ACPI
> tells us everything we need to know. That's backwards.
>
> We shouldn't need an option to tell Linux that the firmware is
> trustworthy. We should have an option to *ignore* it for the times
> when we trip over something broken and haven't figured out a way to
> work around it yet.
other system may have broken _CRS.
maybe we could try to use DMI whitelist them?
YH
next prev parent reply other threads:[~2009-04-27 20:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 1:35 [PATCH] x86/pci: do assign root bus res if _CRS is used Yinghai Lu
2009-04-22 22:08 ` Jesse Barnes
2009-04-27 19:44 ` Bjorn Helgaas
2009-04-27 19:53 ` Jesse Barnes
2009-04-27 20:15 ` Yinghai Lu [this message]
2009-04-27 20:39 ` Bjorn Helgaas
2009-04-27 21:00 ` Yinghai Lu
2009-04-27 22:24 ` Bjorn Helgaas
2009-04-28 2:07 ` Yinghai Lu
2009-04-29 23:08 ` Bjorn Helgaas
2009-04-30 15:14 ` Bjorn Helgaas
2009-05-08 22:40 ` Bjorn Helgaas
2009-05-20 23:49 ` Jesse Barnes
2009-05-21 0:10 ` Yinghai Lu
2009-05-21 14:46 ` Bjorn Helgaas
2009-05-21 16:37 ` Gary Hade
2009-05-27 19:41 ` Gary Hade
2009-06-11 18:00 ` Jesse Barnes
2009-06-16 21:54 ` Jesse Barnes
2009-04-30 0:06 ` Gary Hade
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=49F61265.10201@kernel.org \
--to=yinghai@kernel.org \
--cc=achiang@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=garyhade@us.ibm.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).