From: Jesse Barnes <jesse.barnes@intel.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel MTRR Patch
Date: Mon, 25 Jun 2007 11:23:22 -0700 [thread overview]
Message-ID: <200706251123.24194.jesse.barnes@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706241627130.5819@p34.internal.lan>
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
prev parent reply other threads:[~2007-06-25 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 20:27 Intel MTRR Patch Justin Piszcz
2007-06-25 18:23 ` Jesse Barnes [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200706251123.24194.jesse.barnes@intel.com \
--to=jesse.barnes@intel.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox