From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: thockin@hockin.org
Cc: Greg KH <greg@kroah.com>, Tejun Heo <htejun@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
Kumar Gala <galak@kernel.crashing.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: proper way to assign fixed PCI resources to a "hotplug" device
Date: Thu, 9 Mar 2006 00:21:53 +0300 [thread overview]
Message-ID: <20060309002153.A9651@jurassic.park.msu.ru> (raw)
In-Reply-To: <20060308164041.GA31828@hockin.org>; from thockin@hockin.org on Wed, Mar 08, 2006 at 08:40:42AM -0800
On Wed, Mar 08, 2006 at 08:40:42AM -0800, thockin@hockin.org wrote:
> Assigned from what pool? BIOS most likely sizes the hole to be a pretty
> tight fit for all the resources it knows about. If there is suddenly a
> new resource, you're in trouble.
This can only be true when device in question is behind a pci-to-pci
bridge (which is obviously not the case for ICH controllers you mentioned).
Otherwise we have plenty of MMIO space.
> We could teach linux about chipsets and let Linux re-do the whole
> PCI-allocation process. But that's not an easy task, and is probably a
> contentious idea.
Linux knows how to do this for years. Actually, this is the way how alpha
and some other platforms work. Since 2.6.13, this pretty much applies to
x86 as well (we do respect BIOS PCI allocations, but we clean the things
up after BIOS quite aggressively - see pci_assign_unassigned_resources() call).
Ivan.
next prev parent reply other threads:[~2006-03-08 21:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 17:42 Kumar Gala
2006-03-03 22:07 ` Greg KH
2006-03-03 22:39 ` Kumar Gala
2006-03-03 23:18 ` Greg KH
2006-03-03 23:28 ` Kumar Gala
2006-03-03 23:50 ` Scott Murray
2006-03-09 16:49 ` Kumar Gala
2006-03-03 23:18 ` Jeff Garzik
2006-03-08 2:00 ` Greg KH
2006-03-08 2:31 ` Tejun Heo
2006-03-08 5:27 ` Greg KH
2006-03-08 11:39 ` Ivan Kokshaysky
2006-03-08 16:40 ` thockin
2006-03-08 21:21 ` Ivan Kokshaysky [this message]
2006-03-08 21:57 ` thockin
2006-03-08 22:11 ` Ivan Kokshaysky
2006-03-08 23:54 ` thockin
2006-03-03 23:13 ` Kumar Gala
2006-03-03 23:27 ` Greg KH
2006-03-03 23:40 ` Scott Murray
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=20060309002153.A9651@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=galak@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=thockin@hockin.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®