From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Anders Eriksson <aeriksson@fastmail.fm>,
Peter Anvin <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Sergei Shtylyov <sshtylyov@ru.mvista.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mtrr failure, 3.1-rc1
Date: Thu, 25 Aug 2011 10:43:01 -0700 [thread overview]
Message-ID: <1314294182.16133.19.camel@sbsiddha-desk.sc.intel.com> (raw)
In-Reply-To: <20110825164649.GL2803@mtj.dyndns.org>
On Thu, 2011-08-25 at 09:46 -0700, Tejun Heo wrote:
> Hello,
>
> On Thu, Aug 25, 2011 at 08:55:12AM -0700, Linus Torvalds wrote:
> > Hmm. Some of those commits are marked for stable too.
> >
> > I'm adding appropriate parties to the discussion (authors and
> > sign-offs from the five commits that that merge brings in), but it
> > would also be great if you could bisect exactly which commit broke for
> > you. You can make it quick by just doing
> >
> > git bisect start
> > git bisect bad dc43d9fa73d82083656fb9c02f4823bcdcfb9f91
> > git bisect good dc43d9fa73d82083656fb9c02f4823bcdcfb9f91^
> >
> > and it should take just a couple of tests. I *assume* it's the
> > stop_machine changes by Tejun &co, but who knows..
> >
> > Anders, is this a single-CPU system?
>
> Indeed, while removing custom rendezvous code and switching to
> stop_machine, commit 192d8857427d "x86, mtrr: use stop_machine APIs
> for doing MTRR rendezvous" completely dropped mtrr setting code on
> !CONFIG_SMP.
oops. My bad. Linus, Bad commit is not marked for stable.
I was able to reproduce the issue and tested the below patch. It looks
good.
Thanks.
Acked-by: Suresh Siddha <suresh.b.siddha@intel.com>
>
> Anders, if your kernel didn't have SMP turned on, can you please
> verify the following patch fixes the problem?
>
> Thanks.
>
> diff --git a/arch/x86/kernel/cpu/mtrr/main.c b/arch/x86/kernel/cpu/mtrr/main.c
> index 08119a3..6b96110 100644
> --- a/arch/x86/kernel/cpu/mtrr/main.c
> +++ b/arch/x86/kernel/cpu/mtrr/main.c
> @@ -149,7 +149,6 @@ struct set_mtrr_data {
> */
> static int mtrr_rendezvous_handler(void *info)
> {
> -#ifdef CONFIG_SMP
> struct set_mtrr_data *data = info;
>
> /*
> @@ -171,7 +170,6 @@ static int mtrr_rendezvous_handler(void *info)
> } else if (mtrr_aps_delayed_init || !cpu_online(smp_processor_id())) {
> mtrr_if->set_all();
> }
> -#endif
> return 0;
> }
>
next prev parent reply other threads:[~2011-08-25 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 7:03 Anders Eriksson
2011-08-25 15:55 ` Linus Torvalds
2011-08-25 16:46 ` Tejun Heo
2011-08-25 17:21 ` anders eriksson
2011-08-25 17:43 ` Suresh Siddha [this message]
2011-08-25 17:43 ` Linus Torvalds
2011-08-25 17:46 ` [PATCH] mtrr: fix UP breakage caused during switch to stop_machine Tejun Heo
2011-08-25 18:00 ` H. Peter Anvin
2011-08-25 18:03 ` Linus Torvalds
2011-08-25 19:47 ` mtrr failure, 3.1-rc1 anders eriksson
2011-08-25 22:10 ` Bob Tracy
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=1314294182.16133.19.camel@sbsiddha-desk.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=aeriksson@fastmail.fm \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sshtylyov@ru.mvista.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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®