From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.3-rc6
Date: Thu, 8 Mar 2012 13:18:32 -0800 [thread overview]
Message-ID: <20120308211832.GU2348@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120307121138.GB5237@x1.osrc.amd.com>
On Wed, Mar 07, 2012 at 01:11:38PM +0100, Borislav Petkov wrote:
> On Wed, Mar 07, 2012 at 11:32:27AM +0100, Borislav Petkov wrote:
> > On Sat, Mar 03, 2012 at 06:57:31PM -0800, Linus Torvalds wrote:
> > > Hmm. Nothing much to say about this -rc: it really is all small fixes
> > > and cleanups.
> > >
> > > In fact, it's been calm enough that this *might* be the last -rc, but
> > > we'll see how the upcoming week goes. If it stays calm (and hopefully
> > > even calms down some more), there doesn't seem to be any major reason
> > > to drag out the release cycle any more.
> > >
> > > But hey, that does imply that people who have seen regressions should
> > > re-check them and holler loudly if they are still seeing problems.
> >
> > Just a couple of warnings, just saw them when booted
> > 3.3.0-rc6-00104-gf3969bf78f14 yesterday on this box. I'm ccing Paul for
> > the first two,
>
> Ok, looks like Paul knows about those already:
> http://marc.info/?l=linux-kernel&m=132744022215850 and further.
>
> @Paul: which patch is the latest adding rcu_idle_enter/_exit() calls to pm_idle
> assignees, which you'd like me to test?
This one, which defines RCU_NONIDLE(): https://lkml.org/lkml/2012/2/3/498
And then the following patch on top of that.
Thanx, Paul
------------------------------------------------------------------------
x86: Protect printk() in amd_e400_idle() with RCU_NONIDLE()
Because printk() uses RCU, it cannot be used in the idle loop unless
enclosed by RCU_NONIDLE(). This commit makes the required adjustment.
Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
index 15763af..b185a32 100644
--- a/arch/x86/kernel/process.c
+++ b/arch/x86/kernel/process.c
@@ -552,7 +552,9 @@ static void amd_e400_idle(void)
amd_e400_c1e_detected = true;
if (!boot_cpu_has(X86_FEATURE_NONSTOP_TSC))
mark_tsc_unstable("TSC halt in AMD C1E");
- printk(KERN_INFO "System has AMD C1E enabled\n");
+ RCU_NONIDLE(
+ printk(KERN_INFO "System has AMD C1E enabled\n");
+ );
}
}
next prev parent reply other threads:[~2012-03-09 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 2:57 Linux 3.3-rc6 Linus Torvalds
2012-03-04 6:45 ` Stephen Rothwell
2012-03-07 10:32 ` Borislav Petkov
2012-03-07 12:11 ` Borislav Petkov
2012-03-08 21:18 ` Paul E. McKenney [this message]
2012-03-10 15:16 ` Borislav Petkov
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=20120308211832.GU2348@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.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 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.