From: Markus Kohm <jabber@gmx.org>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
trenn@novell.com, Rafael Wysocki <rjw@novell.com>,
Venkatesh Pallipadi <venki@google.com>
Subject: Re: [patch] x86, mtrr: avoid MTRR reprogramming on BP during boot on UP platforms
Date: Thu, 3 Feb 2011 09:05:13 +0100 [thread overview]
Message-ID: <201102030905.14826@komascript.de> (raw)
In-Reply-To: <1296694975.4418.402.camel@sbsiddha-MOBL3.sc.intel.com>
Suresh Siddha wrote on Thursday 03 February 2011:
> diff --git a/arch/x86/kernel/cpu/mtrr/main.c
> b/arch/x86/kernel/cpu/mtrr/main.c index 01c0f3e..4fe5ebc 100644
> --- a/arch/x86/kernel/cpu/mtrr/main.c
> +++ b/arch/x86/kernel/cpu/mtrr/main.c
> @@ -793,13 +793,21 @@ void set_mtrr_aps_delayed_init(void)
> }
>
> /*
> - * MTRR initialization for all AP's
> + * Delayed MTRR initialization for all AP's
> */
> void mtrr_aps_init(void)
> {
> if (!use_intel())
> return;
>
> + /*
> + * Check if someone has requested the delay of AP MTRR
> initialization, + * by doing set_mtrr_aps_delayed_init(), prior to
> this point. If not, + * then we are done.
> + */
> + if (!mtrr_aps_delayed_init)
> + return;
> +
> set_mtrr(~0U, 0, 0, 0);
> mtrr_aps_delayed_init = false;
> }
ACK
I've tested with kernel 2.6.38-rc3. The hard hang regression is fixed.
Thank you very much!
next prev parent reply other threads:[~2011-02-03 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 1:02 [patch] x86, mtrr: avoid MTRR reprogramming on BP during boot on UP platforms Suresh Siddha
2011-02-03 8:05 ` Markus Kohm [this message]
2011-02-03 14:09 ` [tip:x86/urgent] x86, mtrr: Avoid " tip-bot for Suresh Siddha
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=201102030905.14826@komascript.de \
--to=jabber@gmx.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@novell.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=trenn@novell.com \
--cc=venki@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.