linux-kernel - Re: [regression, bisected] Xonar DX invalid PCI I/O range since 977d17bb174

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Apr 2010 08:54:08 -0700
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Yinghai <yinghai.lu@...cle.com>
Cc:	Peter Henriksson <peter.henriksson@...il.com>,
	Clemens Ladisch <clemens@...isch.de>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [regression, bisected] Xonar DX invalid PCI I/O range since 
 977d17bb174

On Tue, 20 Apr 2010 23:06:09 -0700
Yinghai <yinghai.lu@...cle.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/