linux-kernel - Re: [PATCH] large pci adress space in pci/probe.c for linux-2.6.18

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <86802c440611200759t6c6bbac9od4a3837a05906760@mail.gmail.com>
Date:	Mon, 20 Nov 2006 07:59:19 -0800
From:	"Yinghai Lu" <yinghai.lu@....com>
To:	yadviga <yadviga@...mvista.com>, "Greg KH" <gregkh@...e.de>,
	"Andrew Morton" <akpm@...l.org>
Cc:	"Linux Kernel ML" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] large pci adress space in pci/probe.c for linux-2.6.18

On 11/20/06, yadviga <yadviga@...mvista.com> wrote:
> This is a request from Cisco to update pci address space for 64-bit mips
> Cavium Octeon.
>
> The size returned by a 4GB or greater sized BAR register returns zero
> which made the algorithm in pci_read_bases() hit a continue instead of
> continuing to read the upper 32-bits of the address space. I needed to
> add the code to check if it was a 64-bit memory space by checking the
> relevant lower bits, in which case the lower 32-bits of the size are
> 0xffffffff by the way they calculate size. As far as I can tell this has
> still not been fixed in the latest release of Linux which is 2.6.18. I
> guess no one has
> encountered such a large BAR register yet.
>

There is one version and it is G HK tree. and Adrew has cleaned that code.

for AMD K8 system with co-processor installed in opteron socket, the
co-processor may have 4G above ram installed.

YH
-
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/