From: Ira Weiny <iweiny@acm.org>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: pmu_suspend/resume
Date: Sat, 11 Aug 2001 20:57:07 -0700 [thread overview]
Message-ID: <3B75FE93.DC81EBFE@acm.org> (raw)
I have been using pmu_suspend and pmu_resume to keep my TiBook from
turning off when debugging some kernel stuff. Is this ok?
The reason I ask is that pmu_suspend seems to have the desired effect,
temporarily turning off the PMU. But pmu_resume does not seem to leave
the PMU in a stable state. Now I realize that I am debuging a kernel
and that it could/probably is other factors which are causing these
problems but I just wanted to make sure that there is not some better
way of disabiling the PMU or that I might be using these functions
incorrectly.
Basically:
pmu_suspend();
/* suspicious/known bad code here */
pmu_resume();
Just like that right?
Thanks,
Ira Weiny
iweiny@acm.org
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-12 3:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 3:57 Ira Weiny [this message]
2001-08-12 17:36 ` pmu_suspend/resume Benjamin Herrenschmidt
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=3B75FE93.DC81EBFE@acm.org \
--to=iweiny@acm.org \
--cc=linuxppc-dev@lists.linuxppc.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).