From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Pavel Machek <pavel@ucw.cz>,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH 5/7] PM: PM notifier error injection
Date: Fri, 8 Jul 2011 19:43:20 +0200 [thread overview]
Message-ID: <201107081943.20482.rjw@sisk.pl> (raw)
In-Reply-To: <CAC5umyifMvVTG29JyvBtc_YThorK=AZHZypheUvbtvmShnbTog@mail.gmail.com>
On Friday, July 08, 2011, Akinobu Mita wrote:
> >> --- a/kernel/power/main.c
> >> +++ b/kernel/power/main.c
> >> @@ -42,6 +42,36 @@ int pm_notifier_call_chain(unsigned long val)
> >> return notifier_to_errno(ret);
> >> }
> >>
> >> +#ifdef CONFIG_PM_NOTIFIER_ERROR_INJECTION
> >> +
> >> +static struct err_inject_notifier_block err_inject_pm_notifier = {
> >> + .actions = {
> >> + { ERR_INJECT_NOTIFIER_ACTION(PM_HIBERNATION_PREPARE) },
> >> + { ERR_INJECT_NOTIFIER_ACTION(PM_SUSPEND_PREPARE) },
> >> + { ERR_INJECT_NOTIFIER_ACTION(PM_RESTORE_PREPARE) },
> >> + {}
> >
> > Why have you omitted the PM_POST_* actions?
>
> Because the callbacks of PM_POST_* are not supposed to fail (i.e.
> the return value of pm_notifier_call() is ignored).
OK, fair enough.
> >> --- a/lib/Kconfig.debug
> >> +++ b/lib/Kconfig.debug
> >> @@ -1043,6 +1043,14 @@ config CPU_NOTIFIER_ERROR_INJECTION
> >> # echo 0 > /sys/devices/system/cpu/cpu1/online
> >> bash: echo: write error: Operation not permitted
> >>
> >> +config PM_NOTIFIER_ERROR_INJECTION
> >> + bool "PM notifier error injection"
> >> + depends on PM_DEBUG && NOTIFIER_ERROR_INJECTION
> >> + help
> >> + This option provides the ability to inject artifical errors to
> >> + PM notifier chain callbacks. It is controlled through debugfs
> >> + interface under /sys/kernel/debug/pm-notifier-error-inject/
> >
> > I'm not sure the help is necessary. I think it should be selected
> > automatically if both PM_DEBUG and NOTIFIER_ERROR_INJECTION are set.
>
> OK, I'll try to tweak the option to be better.
Thanks!
Rafael
next prev parent reply other threads:[~2011-07-08 17:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-03 14:16 [PATCH 0/7] notifier error injection Akinobu Mita
2011-07-03 14:16 ` [PATCH 1/7] pm: improve error code of pm_notifier_call_chain() Akinobu Mita
2011-07-03 17:15 ` Pavel Machek
2011-07-04 5:32 ` Akinobu Mita
2011-07-07 21:06 ` Rafael J. Wysocki
2011-07-08 15:50 ` Akinobu Mita
2011-07-08 18:59 ` Rafael J. Wysocki
2011-07-03 14:16 ` [PATCH 2/7] debugfs: add debugfs_create_int Akinobu Mita
2011-07-03 16:23 ` Greg KH
2011-07-04 5:31 ` Akinobu Mita
2011-07-04 15:32 ` Greg KH
2011-07-05 4:42 ` Akinobu Mita
2011-07-03 14:16 ` [PATCH 3/7] fault-injection: notifier error injection Akinobu Mita
2011-07-03 17:16 ` Pavel Machek
2011-07-04 5:35 ` Akinobu Mita
2011-07-03 14:16 ` [PATCH 4/7] cpu: CPU " Akinobu Mita
2011-07-03 14:16 ` [PATCH 5/7] PM: PM " Akinobu Mita
2011-07-07 21:14 ` Rafael J. Wysocki
2011-07-08 15:56 ` Akinobu Mita
2011-07-08 17:43 ` Rafael J. Wysocki [this message]
2011-07-03 14:16 ` [PATCH 6/7] memory: memory " Akinobu Mita
2011-07-03 14:16 ` [PATCH 7/7] powerpc: pSeries reconfig " Akinobu Mita
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=201107081943.20482.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
/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