linux-kernel - Re: Intel MTRR Patch

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: <200706251123.24194.jesse.barnes@intel.com>
Date:	Mon, 25 Jun 2007 11:23:22 -0700
From:	Jesse Barnes <jesse.barnes@...el.com>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Intel MTRR Patch

On Sunday, June 24, 2007 1:27:46 Justin Piszcz wrote:
> Still patches clean against 2.6.22-rc5 incase anyone wanted to know:
>
> # patch -p1 < ../mtrr-v2.patch
> patching file Documentation/kernel-parameters.txt
> patching file arch/i386/kernel/cpu/mtrr/generic.c
> patching file arch/i386/kernel/cpu/mtrr/if.c
> patching file arch/i386/kernel/cpu/mtrr/main.c
> patching file arch/i386/kernel/cpu/mtrr/mtrr.h
> patching file arch/x86_64/kernel/bugs.c
> patching file arch/x86_64/kernel/setup.c
> patching file include/asm-x86_64/mtrr.h

I'm planning on releasing an updated version today, with the changes 
Eric pointed out were necessary (mainly not running it on non-Intel 
CPUs, since AMD maps high memory differently).  But it's good to see 
that the forward porting part of it will be easy. :)

I'm shooting for inclusion post 2.6.22, since I think the change is a 
bit too intrusive (mucking with early boot code) to push it before 
that.

Thanks,
Jesse
-
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/