linux-kernel - Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?

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]

Message-ID: <20070601202416.GL7217@one.firstfloor.org>
Date:	Fri, 1 Jun 2007 22:24:16 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Jesse Barnes <jbarnes@...tuousgeek.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?

> 1. The MCH/ICH8 hub 'requires' a minimum of 512MB to run, the board manual 
> states it needs at least 512MB of memort.
> 2. The DVT/IGP graphics uses either 128MB or 256MB, I have it set to 
> 128MB.
> 
> How can the Linux kernel find this out/poll this information so users do 
> not have to know mem=XXXXM?

I don't think it should. The Linux kernel is not trying to be
a BIOS replacement and should not know everything about the platforms
it runs on.   We sometimes try to work around very common
bugs, but this one (involving lots of memory and special configuration)
seems to be more in the exotic range where command line options
or waiting for a BIOS update seem better options.

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