From: Pavel Machek <pavel@suse.cz>
To: John Levon <levon@movementarian.org>
Cc: Mikael Pettersson <mikpe@csd.uu.se>,
ak@suse.de, linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: Switch APIC to driver model (and make S3 sleep with APIC on)
Date: Mon, 3 Feb 2003 16:40:08 +0100 [thread overview]
Message-ID: <20030203154008.GC480@elf.ucw.cz> (raw)
In-Reply-To: <20030203103254.GA25619@compsoc.man.ac.uk>
Hi!
> > This one should be okay. [oprofile not tested because I don't know how
> > to use it...
>
> It's not hard you know[1].
should apt-get install oprofile then opcontrol --setup
--vmlinux=/boot/vmlinux --ctr0-count=20000
--ctr0-event=CPU_CLK_UNHALTED && opcontrol --start
do the trick? If that works does it mean oprofile is okay?
> > -struct pm_dev * set_nmi_pm_callback(pm_callback callback)
> > +static int nmi_resume(struct device *dev, u32 level)
> > {
> > - apic_pm_unregister(nmi_pmdev);
> > - return apic_pm_register(PM_SYS_DEV, 0, callback);
> > -}
> > + if (level != RESUME_POWER_ON)
> > + return 0;
> > + setup_apic_nmi_watchdog();
> > + return 0;
>
> I don't pretend to understand the PM layer at all, but it looks like
> that both nmi.c's and oprofile's resume functions will get called. This
> won't work: if oprofile has control of the perfctr's/nmi stuff, you
> can't let the NMI watchdog's resume() be called, as it may conflict with
> what oprofile is trying to resume.
oprofile() should already have checks to prevent that, and I added one
[ if (nmi_watchdog == NMI_LOCAL_APIC)
]
to nmi.c. I hope that's okay.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2003-02-03 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 1:21 Switch APIC to driver model (and make S3 sleep with APIC on) Mikael Pettersson
2003-01-28 9:26 ` Pavel Machek
2003-02-02 12:42 ` Pavel Machek
2003-02-03 10:32 ` John Levon
2003-02-03 15:40 ` Pavel Machek [this message]
2003-02-03 20:20 ` John Levon
2003-02-03 21:18 ` Pavel Machek
2003-02-03 23:43 ` John Levon
2003-02-05 21:39 ` Pavel Machek
2003-02-07 11:18 ` John Levon
2003-02-03 12:02 ` Zwane Mwaikambo
2003-02-04 22:55 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-01-28 12:19 Mikael Pettersson
2003-01-29 20:18 ` Pavel Machek
2003-01-29 22:42 ` John Levon
2003-01-29 22:51 ` Pavel Machek
2003-01-20 22:25 Pavel Machek
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=20030203154008.GC480@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=torvalds@transmeta.com \
/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