From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Yinghai <yinghai.lu@oracle.com>
Cc: Peter Henriksson <peter.henriksson@gmail.com>,
Clemens Ladisch <clemens@ladisch.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression, bisected] Xonar DX invalid PCI I/O range since 977d17bb174
Date: Wed, 21 Apr 2010 08:54:08 -0700 [thread overview]
Message-ID: <20100421085408.33754cd0@virtuousgeek.org> (raw)
In-Reply-To: <4BCE95D1.6070105@oracle.com>
On Tue, 20 Apr 2010 23:06:09 -0700
Yinghai <yinghai.lu@oracle.com> wrote:
> after several times retry, mmio ranges get assigned, but io port range can be allocated enough range. it needs 16k,
> but under 05:01.0 to 08:00.0 and 09:04.0 orginal io port from BIOS allocation get lost.
>
> wonder be good, if We can restore it for such case.
>
> current may have to disable bridge resizing feature by default.
>
> can you send out
> lspci -vvxxx
> lspci -tv
Since we don't really know which devices will be in use until drivers
load (and not even then if they're userspace drivers), it might be best
to put off the reassignment until a PCI driver expresses an interest in
the range.
At least, it seems like that would be closer to the ideal approach than
trying to reassign everything at boot, potentially making devices that
don't matter get resources and leaving important devices disabled.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-04-21 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 6:56 [regression, bisected] Xonar DX invalid PCI I/O range since 977d17bb174 Clemens Ladisch
2010-04-19 7:44 ` Peter Henriksson
2010-04-19 8:06 ` Clemens Ladisch
2010-04-19 8:42 ` Peter Henriksson
[not found] ` <4BCCA5FD.6060002@oracle.com>
2010-04-19 19:42 ` Peter Henriksson
2010-04-20 6:41 ` Yinghai
2010-04-20 8:03 ` Peter Henriksson
2010-04-20 17:22 ` Yinghai Lu
2010-04-20 18:45 ` Peter Henriksson
2010-04-21 6:06 ` Yinghai
2010-04-21 9:06 ` Peter Henriksson
2010-04-21 15:54 ` Jesse Barnes [this message]
2010-05-10 19:07 ` Peter Henriksson
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=20100421085408.33754cd0@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=peter.henriksson@gmail.com \
--cc=yinghai.lu@oracle.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