linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-pm@vger.kernel.org, Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [PATCH 1/2] x86 thermal: Delete power-limit-notification console messages
Date: Tue, 28 May 2013 10:17:10 +0800	[thread overview]
Message-ID: <1369707430.1913.3.camel@rzhang1-mobl4> (raw)
In-Reply-To: <f0a8f9faefa8da662d5450ea90db7e8e4d943e25.1368740425.git.len.brown@intel.com>

On Tue, 2013-05-21 at 15:35 -0400, Len Brown wrote:
> From: Fenghua Yu <fenghua.yu@intel.com>
> 
> Package power limits are common on some systems under some conditions --
> so printing console messages when limits are reached
> causes unnecessary customer concern and support calls.
> 
> Note that even with these console messages gone,
> the events can still be observed via system counters:
> 
> $ grep TRM /proc/interrupts
> 
> Shows total thermal interrupts, which includes both power
> limit notifications and thermal throttling interrupts.
> 
> $ grep . /sys/devices/system/cpu/cpu*/thermal_throttle/*
> 
> Will show what caused those interrupts, core and package
> throttling and power limit notifications.
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=36182
> 
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
> Signed-off-by: Len Brown <len.brown@intel.com>

who should take these two patches?

thanks,
rui
> ---
>  arch/x86/kernel/cpu/mcheck/therm_throt.c | 9 ---------
>  1 file changed, 9 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/mcheck/therm_throt.c b/arch/x86/kernel/cpu/mcheck/therm_throt.c
> index 47a1870..68fa890 100644
> --- a/arch/x86/kernel/cpu/mcheck/therm_throt.c
> +++ b/arch/x86/kernel/cpu/mcheck/therm_throt.c
> @@ -181,11 +181,6 @@ static int therm_throt_process(bool new_event, int event, int level)
>  				this_cpu,
>  				level == CORE_LEVEL ? "Core" : "Package",
>  				state->count);
> -		else
> -			printk(KERN_CRIT "CPU%d: %s power limit notification (total events = %lu)\n",
> -				this_cpu,
> -				level == CORE_LEVEL ? "Core" : "Package",
> -				state->count);
>  		return 1;
>  	}
>  	if (old_event) {
> @@ -193,10 +188,6 @@ static int therm_throt_process(bool new_event, int event, int level)
>  			printk(KERN_INFO "CPU%d: %s temperature/speed normal\n",
>  				this_cpu,
>  				level == CORE_LEVEL ? "Core" : "Package");
> -		else
> -			printk(KERN_INFO "CPU%d: %s power limit normal\n",
> -				this_cpu,
> -				level == CORE_LEVEL ? "Core" : "Package");
>  		return 1;
>  	}
>  



  parent reply	other threads:[~2013-05-28  2:17 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 ` [RESEND] " Len Brown
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 [this message]
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=1369707430.1913.3.camel@rzhang1-mobl4 \
    --to=rui.zhang@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).