linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: 蒲文 <wen.pu@powercore.com.cn>
To: "Michael Ellerman" <mpe@ellerman.id.au>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/opal: add warning for unimplemented OPAL message type
Date: Wed, 9 Dec 2015 16:55:01 +0800	[thread overview]
Message-ID: <tencent_1097DF836527EECD6BF4E6AA@qq.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1914 bytes --]

Hi Michael,

On Wednesday, December 09, 2015 11:17:12 AM Michael Ellerman wrote:
> Hi Wen,
> 
> Thanks for the patch.
> 
> On Tue, 2015-12-08 at 15:30 +0800, wen.pu@powercore.com.cn wrote:
> > I found that there are unimplemented OPAL message types "OPAL_MSG_EPOW"
> > and
> > "OPAL_MSG_DPO" in PowerNV Platform. If skiboot send such messages to
> > kernel, nothing will happen(notifier_call_chain() will silently drop it).
> > So I add a warning to inform what has happened, is it necessary?
> 
> What kernel version are you using?
The kernel version is v4.2.1-openpower2, from the newest version at 
https://github.com/open-power/linux.

> 
> Looking at mainline (4.4-rc4), I do see handlers registered for EPOW and
> DPO:
> 
>  
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/p
> owerpc/platforms/powernv/opal-power.c?#n82
> 
> That code was merged in 4.3.
I do find that EPOW and DPO are registered in kernel 4.3. So maybe in the near 
future it will be merged into open-power/linux.

> 
> 
> In general I don't think we want to warn for unhandled message types,
> because we support old kernels running on new skiboot. In that case if we
> warned on every unhandled message we'd potentially spam the console with
> warnings.
> 
> But perhaps we can come up with something smarter, that only warns once for
> each unhandled message type, or something like that? Did you have a bug that
> would have been easier to debug with a warning here?
Yes, I think it is a good idea that only warns once, or warns every a few 
seconds. 
I found that EPOW and DPO only used in IBM FSP platform, not in Habanero 
platform that I had. So I modified the skiboot code and sent a EPOW/DPO message 
to kernel, and found that kernel warn nothing. I have no bug with a warning 
here, and just get a log message via dmesg.

> 
> cheers

Thanks!
Wen Pu

[-- Attachment #2: Type: text/html, Size: 2151 bytes --]

             reply	other threads:[~2015-12-09  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  8:55 蒲文 [this message]
2015-12-11  0:51 ` [PATCH] powerpc/opal: add warning for unimplemented OPAL message type Stewart Smith
  -- strict thread matches above, loose matches on Subject: below --
2015-12-08  7:30 wen.pu
2015-12-09  0:17 ` Michael Ellerman
2015-12-09  8:56   ` Wen Pu

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=tencent_1097DF836527EECD6BF4E6AA@qq.com \
    --to=wen.pu@powercore.com.cn \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).