From: Andi Kleen <ak@suse.de>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386/x86-64 Add nmi watchdog support for new Intel CPUs
Date: Fri, 23 Jun 2006 14:35:38 +0200 [thread overview]
Message-ID: <200606231435.38496.ak@suse.de> (raw)
In-Reply-To: <20060514185023.A16695@unix-os.sc.intel.com>
On Monday 15 May 2006 03:50, Venkatesh Pallipadi wrote:
>
> [Sorry if this is a duplicate. I tried sending this mail two days back and I don't
> see it on the mailing list yet. So, resending it.]
>
>
>
> Intel now has support for Architectural Performance Monitoring Counters
> ( Refer to IA-32 Intel Architecture Software Developer's Manual
> http://www.intel.com/design/pentium4/manuals/253669.htm ). This
> feature is present starting from Intel Core Duo and Intel Core Solo processors.
>
> What this means is, the performance monitoring counters and some performance
> monitoring events are now defined in an architectural way (using cpuid).
> And there will be no need to check for family/model etc for these architectural
> events.
>
> Below is the patch to use this performance counters in nmi watchdog driver.
> Patch handles both i386 and x86-64 kernels.
FYI - i went back to this old patch again because I temporarily dropped
the NMI rework for 2.6.18. Please let me know if it misses any changes
that you added in later kernels (except for the merge with the newer
code base)
-Andi
prev parent reply other threads:[~2006-06-23 12:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 1:50 [PATCH] i386/x86-64 Add nmi watchdog support for new Intel CPUs Venkatesh Pallipadi
2006-05-15 2:11 ` Andrew Morton
2006-05-15 3:03 ` Venkatesh Pallipadi
2006-05-15 7:22 ` Andi Kleen
2006-05-25 22:54 ` Venkatesh Pallipadi
2006-05-26 7:34 ` Andi Kleen
2006-06-23 12:35 ` Andi Kleen [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=200606231435.38496.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.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