From: Matthew Wilcox <matthew@wil.cx>
To: Rajesh Shah <rajesh.shah@intel.com>
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
Dave Airlie <airlied@gmail.com>,
gregkh@suse.de, ak@suse.de, linux-pci@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org, akpm@osdl.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: i386/x86_84: disable PCI resource decode on device disable
Date: Thu, 4 May 2006 14:33:10 -0600 [thread overview]
Message-ID: <20060504203310.GE9609@parisc-linux.org> (raw)
In-Reply-To: <20060504130156.A3494@unix-os.sc.intel.com>
On Thu, May 04, 2006 at 01:01:57PM -0700, Rajesh Shah wrote:
> Yeah, that's also what some other drivers do. For example, PCI/PCIE
> bridges may support capabilities (like hotplug) that are controlled
> by separate drivers. These drivers don't do pci_disable_device()
> when they unload, since the bridge must continue to decode even
> when the other capability driver is gone.
>
> The problem is that most PCI bridges don't have any "extra"
> resources padded into the address ranges they pass down. It
> would be nice to be able to reuse address space released when
> a device is disabled (e.g. for future hot-add), if it's really
> no longer needed.
You could always reprogram the BARs. But I really wouldn't recommend
this; you'll just fragment the address space.
prev parent reply other threads:[~2006-05-04 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 22:27 i386/x86_84: disable PCI resource decode on device disable Rajesh Shah
2006-05-04 3:16 ` Dave Airlie
2006-05-04 9:44 ` Antonino A. Daplas
2006-05-04 20:01 ` Rajesh Shah
2006-05-04 20:33 ` Matthew Wilcox [this message]
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=20060504203310.GE9609@parisc-linux.org \
--to=matthew@wil.cx \
--cc=adaplas@gmail.com \
--cc=airlied@gmail.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=rajesh.shah@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.