From: Mikael Pettersson <mikpe@csd.uu.se>
To: Will Cohen <wcohen@redhat.com>
Cc: Philippe Elie <phil.el@wanadoo.fr>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
John Levon <levon@movementarian.org>
Subject: Re: [PATCH] oprofile add Pentium Mobile support
Date: Mon, 16 Feb 2004 15:20:10 +0100 [thread overview]
Message-ID: <16432.53658.676333.134293@alkaid.it.uu.se> (raw)
In-Reply-To: <4030CBC3.6060605@redhat.com>
Will Cohen writes:
> Mikael Pettersson wrote:
> > Philippe Elie writes:
> > > From: Will Cohen <wcohen@redhat.com>
> > >
> > > Add oprofile support for Pentium Mobile (P6 core). Pentium Mobile needs
> > > to unmask LVPTC vector, since it doesn't hurt other P6 core based cpus
> > > we do it unconditionally for all these.
> >
> > [Patch talking about the Pentium-M.]
> >
> > I can find no support in Intel's documentation (IA32 Volume 3,
> > 25366813.pdf) that Pentium-M:s need to unmask LVTPC.
> >
> > How certain are you of this? Is this an undocumented hardware
> > quirk? If it is documented, please indicate where.
>
> I have tested it on a Pentium M machine. Without the unmask LVTPC the
> nmi handler collected precisely one interrupt. With the LVTPC unmask the
> OProfile data collection worked normally.
>
> > It's my theory that P4 added the auto-masking to help PEBS
> > buffer overflow situations, but since P-M doesn't have PEBS,
> > they shouldn't have had to change this on P-M as well.
> > OTOH, it's certainly possible they changed it by accident.
>
> My theory is that the Pentium M uses same bus interface and local apic
> as the Pentium M. Thus, the Pentium M shares the Pentium 4 need to
> unmask LVTPC.
Sounds reasonable and is consistent with other P-M vs P6 changes.
> > One way of testing this would be to run a P-M with
> > nmi_watchdog=2. If the NMI counter keeps ticking, then
> > LVTPC does not need unmasking.
>
> Yes, I tested the nmi watchdog and it currently does not work on the
> Pentium M. It doesn't get the later interrupts and states it is stuck.
That confirms the "undocumented HW quirk" theory. Thanks. I'll fix
the (in-kernel) NMI watchdog and (out-of-kernel) perfctr drivers.
/Mikael
prev parent reply other threads:[~2004-02-16 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 22:41 Philippe Elie
2004-02-16 10:23 ` Mikael Pettersson
2004-02-16 13:55 ` Will Cohen
2004-02-16 14:20 ` Mikael Pettersson [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=16432.53658.676333.134293@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=akpm@osdl.org \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phil.el@wanadoo.fr \
--cc=wcohen@redhat.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
all inboxes | Powered by JetHome®