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]
Date:	Mon, 4 Jun 2007 21:23:23 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?

> From their e-mail:
> 
> Note before continuing: Debian* Linux Operating System is not an 
> officially, validated, tested Operating System for the Intel(R) Desktop 
> Board DG965WH 
> (see http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=2375); 
> moreover, we do confirm that "on a system that has 8 GB of system memory 
> installed, it is not possible to use all of the installed memory due to 
> system address space being allocated for other system critical functions." 
> [qtd. on page 43 of the Technical Product Specification (see 
> http://download.intel.com/design/motherbd/wh/D5600801US.pdf)].  Thus, the
> following suggestions are provided AS IS; we cannot guarantee the problem 
> would be fixed afterwards:

They're talking about something different than your issue. If you put in
the fully possible 8GB (4x2GB) then some memory will be lost to the PCI hole
because the desktop ICH can only access 35bits (8GB) in hardware.

That can be up to 2GB in extreme cases, usually <0.5-1GB depending
on how much mapping space your hardware needs.

But if you put in less than 8GB the BIOS is supposed to remap 
the memory around the PCI hole and set up the MTRRs correctly
so that the PCI hole is uncached and the memory around it is cached.

That is 100% the BIOS' responsibility and if it doesn't do that
it is buggy.

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