linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stewart Smith <stewart@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: 蒲文 <wen.pu@powercore.com.cn>
Subject: Re: powerpc/powernv: pr_warn_once on unsupported OPAL_MSG type
Date: Thu, 17 Dec 2015 21:19:12 +1100 (AEDT)	[thread overview]
Message-ID: <20151217101912.B369A1402EC@ozlabs.org> (raw)
In-Reply-To: <1449796103-7700-1-git-send-email-stewart@linux.vnet.ibm.com>

On Fri, 2015-11-12 at 01:08:23 UTC, Stewart Smith wrote:
> When running on newer OPAL firmware that supports sending extra
> OPAL_MSG types, we would print a warning on *every* message received.
> 
> This could be a problem for kernels that don't support OPAL_MSG_OCC
> on machines that are running real close to thermal limits and the
> OCC is throttling the chip. For a kernel that is paying attention to
> the message queue, we could get these notifications quite often.
> 
> Conceivably, future message types could also come fairly often,
> and printing that we didn't understand them 10,000 times provides
> no further information than printing them once.
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>

Applied to powerpc fixes, thanks.

https://git.kernel.org/powerpc/c/98da62b716a3b24ab8e77453

cheers

      parent reply	other threads:[~2015-12-17 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  1:08 [PATCH] powerpc/powernv: pr_warn_once on unsupported OPAL_MSG type Stewart Smith
2015-12-11  2:21 ` Michael Ellerman
2015-12-11  2:43   ` Wen Pu
2015-12-11  6:54   ` Stewart Smith
2015-12-17 10:19 ` Michael Ellerman [this message]

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=20151217101912.B369A1402EC@ozlabs.org \
    --to=mpe@ellerman.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.com \
    --cc=wen.pu@powercore.com.cn \
    /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).