From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/pci: intel bus root res with IOH reading -v2
Date: Mon, 19 Oct 2009 14:17:09 -0600 [thread overview]
Message-ID: <200910191417.10995.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <4ACB839A.2060800@kernel.org>
On Tuesday 06 October 2009 11:51:22 am Yinghai Lu wrote:
> > What is the specific problem solved by this patch? Does "pci=use_crs"
> > address any of that problem? (I know "pci=use_crs" breaks some machines,
> > and I know it's unacceptable to require users to use it. But I want to
> > understand whether the concept is related, and whether you've tripped
> > over a BIOS defect or a Linux pci_root.c defect.)
>
> BIOS doesn't allocate resource to some pci devices when too many devices. and need kernel to allocate resource ( 32bit mmio, 64 mmio)
> to those devices.
> current only known fw that can allocate mmio 64 ( with correct setting) is LinuxBIOS.
>
> also could help os to fend off some range that is wrongly allocated by BIOS that is cross the boundary between different peer root bus.
>
> _CRS doesn't report any MMIO 64 range, even HW does have that set.
This discussion got derailed into "BIOS bad, Linux good" before I
could learn more about the specific problem you're solving.
Can you tell us what machine this fixes? Can you include logs, e.g.,
dmesg/lspci/iomem, that show the problem, and corresponding ones
with your patch applied that show the fix?
Has the machine been released? Does Windows work on it?
I'd also like to know more about the "range that is wrongly allocated
by BIOS that is cross the boundary between different peer root bus."
Does this mean the BIOS programmed the host bridges wrong, or does it
mean it reported something invalid in the host bridge _CRS, or something
else?
Thanks,
Bjorn
prev parent reply other threads:[~2009-10-19 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 4:54 Yinghai Lu
2009-10-06 16:52 ` Jesse Barnes
2009-10-06 17:33 ` Bjorn Helgaas
2009-10-06 17:51 ` Yinghai Lu
2009-10-06 18:57 ` Bjorn Helgaas
2009-10-12 20:34 ` Ingo Molnar
2009-10-12 20:49 ` Jesse Barnes
[not found] ` <200910121545.47794.bjorn.helgaas@hp.com>
2009-10-12 21:49 ` H. Peter Anvin
2009-10-13 7:03 ` Ingo Molnar
2009-10-12 22:14 ` Bjorn Helgaas
2009-10-19 20:17 ` Bjorn Helgaas [this message]
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=200910191417.10995.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@kernel.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
all inboxes | Powered by JetHome®