From: Mahmood Naderan <nt_mahmood@yahoo.com>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: CPU MTRRs and linux kernel
Date: Tue, 12 Jun 2012 08:17:43 -0700 (PDT) [thread overview]
Message-ID: <1339514263.74306.YahooMailNeo@web111722.mail.gq1.yahoo.com> (raw)
In-Reply-To: <20120612135713.GA10128@x1.osrc.amd.com>
>If it were me and I didn't have any particular reason to stick with
>2.6.32, I'd always go for the latest kernel
One thing is not clear for me. Did you make the following change in the latest version today? I want to know, should I wait until it is pushed in to ubuntu repository?
diff --git a/arch/x86/kernel/cpu/mtrr/cleanup.c b/arch/x86/kernel/cpu/mtrr/cleanup.c
index c5f59d071425..ac140c7be396 100644
--- a/arch/x86/kernel/cpu/mtrr/cleanup.c
+++ b/arch/x86/kernel/cpu/mtrr/cleanup.c
@@ -827,7 +827,7 @@ int __init amd_special_default_mtrr(void)
if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD)
return 0;
- if (boot_cpu_data.x86 < 0xf || boot_cpu_data.x86 > 0x11)
+ if (boot_cpu_data.x86 < 0xf)
return 0;
/* In case some hypervisor doesn't pass SYSCFG through: */
if (rdmsr_safe(MSR_K8_SYSCFG, &l, &h) < 0)
// Naderan *Mahmood;
----- Original Message -----
From: Borislav Petkov <bp@alien8.de>
To: Mahmood Naderan <nt_mahmood@yahoo.com>
Cc: LKML <linux-kernel@vger.kernel.org>; Andreas Herrmann <andreas.herrmann3@amd.com>
Sent: Tuesday, June 12, 2012 6:27 PM
Subject: Re: CPU MTRRs and linux kernel
On Tue, Jun 12, 2012 at 06:48:10AM -0700, Mahmood Naderan wrote:
> Thanks Borislav, I want to know, should I upgrade to the latest kernel
> or it is possible to download the source of 2.6.32-24 from repository
> and modify cleanup.c and then recompile?
Whatever you decide.
If it were me and I didn't have any particular reason to stick with
2.6.32, I'd always go for the latest kernel.
In any case, no matter which kernel you're installing, just make sure it
contains the aforementioned patch which should fix your problem.
HTH.
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-06-12 15:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 9:37 Mahmood Naderan
2012-06-12 10:12 ` Alan Cox
[not found] ` <1339496451.43175.YahooMailNeo@web111722.mail.gq1.yahoo.com>
2012-06-12 10:23 ` Mahmood Naderan
2012-06-12 10:39 ` Borislav Petkov
2012-06-12 13:48 ` Mahmood Naderan
2012-06-12 13:57 ` Borislav Petkov
2012-06-12 15:17 ` Mahmood Naderan [this message]
2012-06-12 13:59 ` Andreas Herrmann
2012-06-12 15:13 ` Stefan Bader
2012-06-12 15:15 ` Mahmood Naderan
2012-06-12 15:17 ` Borislav Petkov
2012-06-12 15:18 ` Mahmood Naderan
2012-06-12 15:31 ` Stefan Bader
2012-06-12 16:38 ` Mahmood Naderan
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=1339514263.74306.YahooMailNeo@web111722.mail.gq1.yahoo.com \
--to=nt_mahmood@yahoo.com \
--cc=andreas.herrmann3@amd.com \
--cc=bp@alien8.de \
--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
all inboxes | Powered by JetHome®