public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Switch APIC to driver model (and make S3 sleep with APIC on)
Date: Mon, 3 Feb 2003 20:20:30 +0000	[thread overview]
Message-ID: <20030203202029.GA99614@compsoc.man.ac.uk> (raw)
In-Reply-To: <20030203154008.GC480@elf.ucw.cz>

On Mon, Feb 03, 2003 at 04:40:08PM +0100, Pavel Machek wrote:

> should apt-get install

not packaged yet I'm afraid. Get
http://movementarian.org/oprofile-0.5.tar.gz, ./configure \
--with-kernel-support && make && make install

> --ctr0-event=CPU_CLK_UNHALTED && opcontrol --start

If it's an Intel CPU (not pentium 4) this should be OK
For Athlon, use INST_RETIRED

> do the trick? If that works does it mean oprofile is okay?

Run a few kernel compiles and stress it a bit. Run "op_time" to check
you get output...

> > 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

I haven't seen where you added these checks. They did not exist before:
oprofile took responsibility for the NMI/perfctr handling off the NMI
watchdog entirely, then handed it back when oprofile finished.

Basically you have to ensure that only the right pm callback is called,
not both.

> [        if (nmi_watchdog == NMI_LOCAL_APIC)

I don't see an added line like this ?

regards
john

  reply	other threads:[~2003-02-03 20:11 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
2003-02-03 20:20       ` John Levon [this message]
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=20030203202029.GA99614@compsoc.man.ac.uk \
    --to=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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