linux-kernel - Re: [PATCH] x86: Allow MMCONFIG above 4GB 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: <87r69xzthp.fsf@basil.nowhere.org>
Date:	Sun, 13 Jul 2008 17:36:18 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	John Keller <jpk@....com>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	takayoshi.kochi@...il.com
Subject: Re: [PATCH] x86: Allow MMCONFIG above 4GB on x86_64

John Keller <jpk@....com> writes:
>
> A similar patch was submitted over a year ago, but apparently was not
> merged in.

There's no reason at all to make this 64bit only. A PAE 32bit kernel
can also access data above 4GB. So an ifdef is the wrong way.

The reason the check is there is that there are lots of 
x86 BIOS that report wrong mmconfig and this way there's another
sanity check.

You'll need either to find a way to preserve this check
on kernels not running on your system or show that the 
sanity check is not needed anymore. The later would 
be likely tricky.

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