From: Gary Hade <garyhade@us.ibm.com>
To: Gary Hade <garyhade@us.ibm.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Thomas Gleixner <tglx@linutronix.de>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Jaswinder Singh Rajput <jaswinder@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
x86 maintainers <x86@kernel.org>, Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Regression with commit f9cde5f in 2.6.30-gitX
Date: Wed, 24 Jun 2009 15:12:57 -0700 [thread overview]
Message-ID: <20090624221257.GA12934@us.ibm.com> (raw)
In-Reply-To: <20090624212424.GH7239@us.ibm.com>
On Wed, Jun 24, 2009 at 02:24:24PM -0700, Gary Hade wrote:
> On Wed, Jun 24, 2009 at 03:05:12PM -0500, Larry Finger wrote:
> > Gary Hade wrote:
> > > On Wed, Jun 24, 2009 at 08:45:31PM +0200, Thomas Gleixner wrote:
> > >> Can we just bring the limit check back and increase the number for now
> > >> until folks come up with a better solution ?
> > >
> > > Another possible option is leaving in the limit check (still valid
> > > IMO for correct behavior of previous 'pci=use_crs') and reverting
> > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9e9f46c44e487af0a82eb61b624553e2f7118f5b
> > > until the better solution for the fixed size array issue is
> > > available.
> >
> > Either increasing PCI_BUS_NUM_RESOURCES from 16 to 20 or 24
>
> Yes, it looks to me like 20 might be the absolute minimum
> that your system could tolerate. The big mystery is how much
> to increase it so we don't see the same problem on other
> systems where _CRS may return some unknown amount more that
^^^^
than
> the 17 resources that are being returned on your system.
>
> > or reverting f9cde5f will work for my system.
>
> This would not be good without also reverting
> 9e9f46c44e487af0a82eb61b624553e2f7118f5b since devices
> below the transparent bridge on your's and other's systems
> may have trouble getting the resources they need.
>
> Removing the check would only hide possibly more insidious
> and difficult to debug problems that could show up later.
> This was the main reason I provided the patch. This kind
> of check should have actually existed prior to
> 9e9f46c44e487af0a82eb61b624553e2f7118f5b when 'pci=use_crs'
> was needed to enable use of the _CRS data.
One additional thing that is interesting about _CRS
returning 17 resources on your system is that even in
the absence of the transparent bridge constraint where
the last 3 slots of the resource array would be available,
there still isn't enough room in that 16 element array for
all 17 resources. Without the check that 17th resource
(apparently not needed for your current configuration)
would be silently ignored.
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-06-24 22:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 1:33 Regression with commit f9cde5f in 2.6.30-gitX Larry Finger
2009-06-24 5:31 ` Larry Finger
2009-06-24 12:16 ` Jaswinder Singh Rajput
2009-06-24 12:22 ` Ingo Molnar
2009-06-24 12:30 ` Jaswinder Singh Rajput
2009-06-24 14:46 ` Gary Hade
2009-06-24 14:21 ` Larry Finger
2009-06-24 15:16 ` Ingo Molnar
2009-06-24 15:19 ` Thomas Gleixner
2009-06-24 15:42 ` Larry Finger
2009-06-24 15:57 ` Jaswinder Singh Rajput
2009-06-24 16:13 ` Gary Hade
2009-06-24 16:33 ` Jaswinder Singh Rajput
2009-06-24 16:44 ` Jesse Barnes
2009-06-24 17:55 ` Gary Hade
2009-06-24 18:28 ` Jesse Barnes
2009-06-24 18:45 ` Thomas Gleixner
2009-06-24 19:48 ` Gary Hade
2009-06-24 20:05 ` Larry Finger
2009-06-24 21:24 ` Gary Hade
2009-06-24 22:12 ` Gary Hade [this message]
2009-06-24 21:32 ` Yinghai Lu
2009-06-24 21:42 ` Larry Finger
2009-06-24 21:44 ` Yinghai Lu
2009-06-24 22:04 ` Larry Finger
2009-06-24 22:11 ` Yinghai Lu
2009-06-24 22:53 ` Yinghai Lu
2009-06-24 23:33 ` Larry Finger
2009-06-24 23:44 ` Linus Torvalds
2009-06-24 19:28 ` Gary Hade
2009-06-24 16:52 ` Larry Finger
2009-06-24 14:51 ` Thomas Gleixner
2009-06-24 15:55 ` Jaswinder Singh Rajput
2009-06-24 16:17 ` Thomas Gleixner
2009-06-24 15:56 ` Gary Hade
2009-06-24 16:15 ` Jaswinder Singh Rajput
2009-06-24 16:33 ` Gary Hade
2009-06-24 16:25 ` Jesse Barnes
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=20090624221257.GA12934@us.ibm.com \
--to=garyhade@us.ibm.com \
--cc=Larry.Finger@lwfinger.net \
--cc=jaswinder@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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