All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: rjw@sisk.pl
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RESEND] [PATCH 0/2]  Quiet power limit notification
Date: Thu, 16 May 2013 17:54:04 -0400	[thread overview]
Message-ID: <1368741246-3998-1-git-send-email-lenb@kernel.org> (raw)
In-Reply-To: <1368625017-6835-1-git-send-email-fenghua.yu@intel.com>

[Re-sending for Fenghua, as his e-mail seems to have got lost.
 In case you receive multiple copies, the patches are unchanged.]

thanks,
-Len Brown
Intel Open Source Technology Center
---

Power Limit Notification (X86_FEATURE_PLN) was added in Sandy Bridge
to give the OS the option of knowing when the package has reached
a configured power threshold.

Linux-2.6.36 enabled this feature:
0199114c31798af5b83841b21759b64171060d9b
(x86, hwmon: Package Level Thermal/Power: power limit)

It enabld the interrupt, and the interrupt hander
added to the MCE log and printed to the console:

printk(KERN_CRIT "CPU%d: %s power limit notification (total events = %lu)
printk(KERN_INFO "CPU%d: %s power limit normal\n"

However, these events are quite routine on some systems under some conditions,
alarming customers and provoking un-necessary customer support calls.

So the MCE log entry was deleted in Linux-3.3:

29e9bf1841e4f9df13b4992a716fece7087dd237
(x86, mce, therm_throt: Don't report power limit and package level thermal throttle events in mcelog)

Here we delete the corresponding kernel console messages,
and then we disable the interrupt by default -- allowing it
to be enabled by cmdline for diagnosis purposes.

https://bugzilla.kernel.org/show_bug.cgi?id=36182

This pair of patches applies cleanly back to Linux-3.3.

Documentation/kernel-parameters.txt      |  2 ++
arch/x86/kernel/cpu/mcheck/therm_throt.c | 43 ++++++++++++++++++++++++++-----------------
 2 files changed, 28 insertions(+), 17 deletions(-)

[1/2] x86 thermal: Disable power limit notification interrupt by default
[2/2] x86 thermal: Delete power-limit-notification console messages

  reply	other threads:[~2013-05-16 21:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 13:36 [PATCH 0/2] Quiet power limit notification Fenghua Yu
2013-05-16 21:54 ` Len Brown [this message]
2013-05-21 16:53   ` [RESEND 2] [PATCH 0/2] Rewrite power limit notification interrupt handling Len Brown
2013-05-21 19:35   ` [PATCH 1/2] x86 thermal: Delete power-limit-notification console messages Len Brown
2013-05-21 19:35     ` [PATCH 2/2] x86 thermal: Disable power limit notification interrupt by default Len Brown
2013-05-22  4:54     ` [PATCH 1/2] x86 thermal: Delete power-limit-notification console messages R, Durgadoss
2013-05-22 23:31       ` Yu, Fenghua
2013-05-28  2:17     ` Zhang Rui
2013-06-25 18:53       ` Yu, Fenghua

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=1368741246-3998-1-git-send-email-lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.