From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Greg KH <gregkh@suse.de>, Adam Jackson <ajackson@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: PCI bridge range sizing bug
Date: Fri, 20 Apr 2007 11:28:42 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704201102000.9964@woody.linux-foundation.org> (raw)
In-Reply-To: <200704200932.52181.jesse.barnes@intel.com>
On Fri, 20 Apr 2007, Jesse Barnes wrote:
>
> Sounds good, hopefully reassigning the bridge resources won't cause too
> much trouble. Do you have time to hack this up? If not, I could give
> it a try, as long as ajax is willing to test...
Actually, I would suggest we not do it automatically (because the need for
it is just so low, and the downsides are potentially huge - there are just
too many resources that are "hidden" from us through ACPI tricks and
having hardware that doesn't actually expose their PCI resources fully
through the normal PCI resource setup).
So I'd suggest that at least initially, we could/should just make it a
decision based on a command line flag like the "pci=assign-busses" thing
is now (which forces bus *numbers* to be re-assigned regardless of how
they were assigned by the firmware, not the actual resources).
Because realistically, I don't think we'll see any common PC platform that
actually needs it. Simply because I seriously doubt Windows reassignes bus
resources either.
Ivan, want to add some way to force that allocation (something like
"pci=assign-bus-resources")
Linus
next prev parent reply other threads:[~2007-04-20 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1175812632.17147.12.camel@localhost.localdomain>
2007-04-19 23:11 ` Jesse Barnes
2007-04-19 23:40 ` Greg KH
2007-04-20 0:19 ` Linus Torvalds
2007-04-20 9:23 ` Ivan Kokshaysky
2007-04-20 16:32 ` Jesse Barnes
2007-04-20 18:28 ` Linus Torvalds [this message]
2007-04-20 20:30 ` Ivan Kokshaysky
2007-05-14 17:45 ` Jesse Barnes
2007-05-15 22:39 ` Ivan Kokshaysky
2007-04-20 20:34 ` Jesse Barnes
2007-04-21 5:31 ` Rik van Riel
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.0.98.0704201102000.9964@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=ajackson@redhat.com \
--cc=gregkh@suse.de \
--cc=ink@jurassic.park.msu.ru \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.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
Powered by JetHome