From: Linus Torvalds <torvalds@linux-foundation.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Gary Hade <garyhade@us.ibm.com>,
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>
Subject: Re: Regression with commit f9cde5f in 2.6.30-gitX
Date: Wed, 24 Jun 2009 16:44:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906241639030.3605@localhost.localdomain> (raw)
In-Reply-To: <4A42B7BC.2000402@lwfinger.net>
On Wed, 24 Jun 2009, Larry Finger wrote:
>
> From what I read in Linus's mails, it may be a moot point; however, my
> system boots with these 3, and only these 3, patches applied.
Well, it's definitely not moot. We want "use_crs" to work, whether it's
the default or not. I just doubt it should be the default (necessarily
ever).
The resources listed in the _CRS table may well be useful to make
decisions on (minimally: "is this a root bridge", but possibly also
scanning decisions). But I seriously doubt it makes any sense to insert
the _CRS resources into the bus resource list.
It might, for example, make sense to add them to the resource tree (after
scanning), the same way we add the e820 resources to the resource tree.
But judging from your dmesg:
pci_bus 0000:00: resource 0 io: [0x00-0xcf7]
pci_bus 0000:00: resource 1 io: [0xd00-0xffff]
pci_bus 0000:00: resource 2 mem: [0x0a0000-0x0bffff]
pci_bus 0000:00: resource 3 mem: [0x0c0000-0x0c3fff]
pci_bus 0000:00: resource 4 mem: [0x0c4000-0x0c7fff]
pci_bus 0000:00: resource 5 mem: [0x0c8000-0x0cbfff]
pci_bus 0000:00: resource 6 mem: [0x0cc000-0x0cffff]
pci_bus 0000:00: resource 7 mem: [0x0d4000-0x0d7fff]
pci_bus 0000:00: resource 8 mem: [0x0d8000-0x0dbfff]
pci_bus 0000:00: resource 9 mem: [0x0dc000-0x0dffff]
pci_bus 0000:00: resource 10 mem: [0x0e0000-0x0e3fff]
pci_bus 0000:00: resource 11 mem: [0x0e4000-0x0e7fff]
pci_bus 0000:00: resource 12 mem: [0x0e8000-0x0ebfff]
pci_bus 0000:00: resource 13 mem: [0x0ec000-0x0effff]
pci_bus 0000:00: resource 14 mem: [0x0f0000-0x0fffff]
pci_bus 0000:00: resource 15 mem: [0xc0000000-0xfebfffff]
pci_bus 0000:01: resource 1 mem: [0xfc100000-0xfc1fffff]
pci_bus 0000:01: resource 3 io: [0x00-0xcf7]
pci_bus 0000:01: resource 4 io: [0xd00-0xffff]
pci_bus 0000:01: resource 5 mem: [0x0a0000-0x0bffff]
pci_bus 0000:01: resource 6 mem: [0x0c0000-0x0c3fff]
pci_bus 0000:01: resource 7 mem: [0x0c4000-0x0c7fff]
pci_bus 0000:01: resource 8 mem: [0x0c8000-0x0cbfff]
pci_bus 0000:01: resource 9 mem: [0x0cc000-0x0cffff]
pci_bus 0000:01: resource 10 mem: [0x0d4000-0x0d7fff]
pci_bus 0000:01: resource 11 mem: [0x0d8000-0x0dbfff]
pci_bus 0000:01: resource 12 mem: [0x0dc000-0x0dffff]
pci_bus 0000:01: resource 13 mem: [0x0e0000-0x0e3fff]
pci_bus 0000:01: resource 14 mem: [0x0e4000-0x0e7fff]
pci_bus 0000:01: resource 15 mem: [0x0e8000-0x0ebfff]
pci_bus 0000:01: resource 16 mem: [0x0ec000-0x0effff]
pci_bus 0000:01: resource 17 mem: [0x0f0000-0x0fffff]
pci_bus 0000:01: resource 18 mem: [0xc0000000-0xfebfffff]
none of those look in any way like sensible "resources" to be put in the
device. Quite frankly, they look like total garbage to me.
Linus
next prev parent reply other threads:[~2009-06-24 23:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 1:33 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
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 [this message]
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=alpine.LFD.2.01.0906241639030.3605@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=garyhade@us.ibm.com \
--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=x86@kernel.org \
--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
Powered by JetHome