From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Len Brown <lenb@kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] PM: Warn if interrupts are enabled during suspend-resume of sysdevs
Date: Sun, 5 Apr 2009 19:39:29 +0200 [thread overview]
Message-ID: <200904051939.30170.rjw@sisk.pl> (raw)
In-Reply-To: <20090405135108.GC25250@elte.hu>
On Sunday 05 April 2009, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@sisk.pl> wrote:
>
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > Sysdev have to be suspended and resumed with interrupts disabled
> > and things usually break in a way that's difficult to debug if one
> > of sysdev drivers enables interrupts by mistake during suspend or
> > resume. Add extra checks that will generate warnings in such
> > cases.
>
> no objections - but obviously the real solution would be to finish
> PeterZ's "detect assymetric kernel functions" patch:
>
> That patch (Peter posted an initial version of it already on lkml)
> works the following way:
>
> the ftrace function-graph-tracer plugin is utilized to instrument
> every function call in the kernel. That is extended with the
> following check: every function except __lockfunc and __sched
> functions must be 'balanced' - i.e. they must enter and exit with
> the same IRQ flags, preempt count and lock depth counter.
Nothing wrong with that, but I'd also like to have checks that don't depend on
ftrace. :-)
Thanks,
Rafael
prev parent reply other threads:[~2009-04-05 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 21:23 Rafael J. Wysocki
2009-04-04 22:03 ` Frans Pop
2009-04-04 22:10 ` Rafael J. Wysocki
2009-04-05 13:51 ` Ingo Molnar
2009-04-05 17:39 ` Rafael J. Wysocki [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=200904051939.30170.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=a.p.zijlstra@chello.nl \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®