From: Gary Hade <garyhade@us.ibm.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Yinghai Lu <yhlu.kernel@gmail.com>, 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: Thu, 21 May 2009 09:37:37 -0700 [thread overview]
Message-ID: <20090521163737.GA7891@us.ibm.com> (raw)
In-Reply-To: <200905210846.18292.bjorn.helgaas@hp.com>
On Thu, May 21, 2009 at 08:46:17AM -0600, Bjorn Helgaas wrote:
> On Wednesday 20 May 2009 5:49:10 pm Jesse Barnes wrote:
> > On Fri, 8 May 2009 16:40:10 -0600
> > Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > > Did anything happen with this?
> > >
> > > The longer we wait to make "use_crs" the default, the harder it
> > > will be, so I'd like to push ahead.
> >
> > Here's a patch to make CRS the default. If it looks ok I can push it
> > into my linux-next branch. I'm all for using reliable data from the
> > BIOS. I guess we'll find out fairly quickly if this stuff isn't...
>
> Thanks for following up on this, Jesse. It was on my to-do list for
> yesterday, but I didn't get to it.
>
> Yinghai mentioned a specific box where we might have trouble, but we
> never got enough details to really debug it. So I think we might as
> well give it a shot and fine-tune it as we need to.
I just remembered that Andrew Morton once raised some concerns
related to the number of _CRS returned resources exceeding the
fixed resource array size -> http://lkml.org/lkml/2007/11/1/49
I believe PCI_BUS_NUM_RESOURCES was later increased but if
that increase was insufficient to cover all systems that the
code will now be exposed to, it seems like the "And should we
really be silently ignoring this problem? Should we at least
report it?" comment that was not addressed could become relevent.
Gary
--
Gary Hade
System x Enablement
IBM Linux Technology Center
503-578-4503 IBM T/L: 775-4503
garyhade@us.ibm.com
http://www.ibm.com/linux/ltc
next prev parent reply other threads:[~2009-05-21 16:37 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
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 [this message]
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=20090521163737.GA7891@us.ibm.com \
--to=garyhade@us.ibm.com \
--cc=achiang@hp.com \
--cc=bjorn.helgaas@hp.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 \
--cc=yhlu.kernel@gmail.com \
/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).