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: <86802c440810251255ncbbed09l9404c03406c61f05@mail.gmail.com>
Date:	Sat, 25 Oct 2008 12:55:59 -0700
From:	"Yinghai Lu" <yinghai@...nel.org>
To:	mathieu.taillefumier@...e.fr
Cc:	"Jesse Barnes" <jbarnes@...tuousgeek.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [Bug] pci allocation resources problems on x86_64

On Sat, Oct 25, 2008 at 5:43 AM,  <mathieu.taillefumier@...e.fr> wrote:
> Hi,
>
> 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.

your BIOS only leave 0xc0000000 - 0xc7ffffff for kernel to allocate
that to unassigned resource.

and your device for bus 0x0a need 0x4000000 for mmio and 0x4000000 for
pref mmio.

but 1f.3 is not assigned resource too, need to make sure if it really
need to assigned resource by OS too...
kernel should allocate 0xca00000 to it..., so simplely use quirks to disable it.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ