linux-kernel - Re: [Bug] pci allocation resources problems on x86

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1224938637.4903148d28cfc@imp.free.fr>
Date:	Sat, 25 Oct 2008 14:43:57 +0200
From:	mathieu.taillefumier@...e.fr
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	mathieu.taillefumier@...e.fr,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [Bug] pci allocation resources problems on x86_64

Hi,

 > and that range it can not use that...
>
> only solution could be
>
> Allocating PCI resources starting at c2000000 (gap: c0000000:20000000)
>
> about pci_mem_start from 0xc1000000 instead of 0xc200000
>
> __init void e820_setup_gap(void)
> {
>         unsigned long gapstart, gapsize, round;
>         int found;
>
>         gapstart = 0x10000000;
>         gapsize = 0x400000;
>         found  = e820_search_gap(&gapstart, &gapsize, 0, MAX_GAP_END);
>
> #ifdef CONFIG_X86_64
>         if (!found) {
>                 gapstart = (max_pfn << PAGE_SHIFT) + 1024*1024;
>                 printk(KERN_ERR "PCI: Warning: Cannot find a gap in the 32bit
> "
>                        "address range\n"
>                        KERN_ERR "PCI: Unassigned devices with 32bit resource
> "
>                        "registers may break!\n");
>         }
> #endif
>
>         /*
>          * See how much we want to round up: start off with
>          * rounding to the next 1MB area.
>          */
>         round = 0x100000;
>         while ((gapsize >> 4) > round)
>                 round += round;
>         /* Fun with two's complement */
>         pci_mem_start = (gapstart + round) & -round;
>
>         printk(KERN_INFO
>                "Allocating PCI resources starting at %lx (gap: %lx:%lx)\n",
>                pci_mem_start, gapstart, gapsize);
> }
>
>
> please check if you can change memhole size in BIOS... if not, we can
> have more patch for it....make pci_mem_start more compact...

It is not possible to modify anything from the bios at least nothing related to
memory. So what do you suggest forcing the pci_mem_start. When I look at the
dmesg file I find some open windows such as 0xc0000001 -> 0xdfffffff and
0xf0000001 -> to 0xfebffffff or something like that.

Mathieu

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


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