linux-kernel - [PATCH 0/4] gart cleanups and fixes

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

Date:	Mon, 18 Apr 2011 15:45:42 +0200
From:	Joerg Roedel <joerg.roedel@....com>
To:	Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
CC:	<x86@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/4] gart cleanups and fixes

Hi,

here is a patch-set to clean things up and fix certain issues with the
GART driver in x86-linux. The first patch changes the alignment
requirements for the aperture to be aper_size instead of hard-coded
512MB as discussed in another thread.
Patch two is preperation for patch three which makes sure that the bit
to disable cache probes on gart table walks is always set, even when the
BIOS sets up the aperture correctly and Linux does not remap then.
The last patch adds a check for a GART hardware constraint. The GART can
only map addresses in the first 1TB of physical memory. This is now
checked with the last patch.

Regards,

	Joerg

Diffstat:

 arch/x86/include/asm/gart.h   |   24 ++++++++++++------------
 arch/x86/kernel/aperture_64.c |   36 ++++++++++++++++++++----------------
 arch/x86/kernel/pci-gart_64.c |    9 ++++++++-
 3 files changed, 40 insertions(+), 29 deletions(-)

Shortlog:

Joerg Roedel (4):
      x86, gart: Don't enforce GART aperture lower-bound by alignment
      x86, gart: Convert spaces to tabs in enable_gart_translation
      x86, gart: Set DISTLBWALKPRB bit always
      x86, gart: Make sure GART does not map physmem above 1TB

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