public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] performance counters 3.1 for 2.5.45 [3/4]: shared glue files
Date: Fri, 1 Nov 2002 00:10:39 +0100 (MET)	[thread overview]
Message-ID: <200210312310.AAA07612@kim.it.uu.se> (raw)

This is part 3 of 4 of perfctr-3.1 for the 2.5.45 kernel:
common glue files.

 Kconfig  |   43 +++++++++++++++++++++++++++++++++++++++++++
 Makefile |   13 +++++++++++++
 2 files changed, 56 insertions(+)

diff -uN linux-2.5.45/drivers/perfctr/Kconfig linux-2.5.45.perfctr-3.1/drivers/perfctr/Kconfig
--- linux-2.5.45/drivers/perfctr/Kconfig	Thu Jan  1 01:00:00 1970
+++ linux-2.5.45.perfctr-3.1/drivers/perfctr/Kconfig	Thu Oct 31 22:36:50 2002
@@ -0,0 +1,43 @@
+# $Id: Kconfig,v 1.1 2002/10/31 21:36:50 mikpe Exp $
+# Performance-monitoring counters driver configuration
+#
+
+menu "Performance-monitoring counters support"
+
+config PERFCTR
+	bool "Performance monitoring counters support"
+	help
+	  This driver provides access to the performance-monitoring counter
+	  registers available in some (but not all) modern processors.
+	  These special-purpose registers can be programmed to count low-level
+	  performance-related events which occur during program execution,
+	  such as cache misses, pipeline stalls, etc.
+
+	  The driver supports most x86-class processors known to have
+	  performance-monitoring counters: Intel Pentium to Pentium 4,
+	  AMD K7, Cyrix 6x86MX/MII/III, VIA C3, and WinChip C6/2/3.
+
+	  On processors which have a time-stamp counter but no performance-
+	  monitoring counters, such as the AMD K6 family, the driver supports
+	  plain cycle-count performance measurements only.
+
+	  On WinChip C6/2/3 processors the performance-monitoring counters
+	  cannot be used unless the time-stamp counter has been disabled.
+	  Please read <file:drivers/perfctr/x86.c> for further information.
+
+	  You can safely say Y here, even if you intend to run the kernel
+	  on a processor without performance-monitoring counters.
+
+config PERFCTR_VIRTUAL
+	bool "Virtual performance counters support"
+	depends on PERFCTR
+	help
+	  The processor's performance-monitoring counters are special-purpose
+	  global registers. This option adds support for virtual per-process
+	  performance-monitoring counters which only run when the process
+	  to which they belong is executing. This improves the accuracy of
+	  performance measurements by reducing "noise" from other processes.
+
+	  Say Y.
+
+endmenu
diff -uN linux-2.5.45/drivers/perfctr/Makefile linux-2.5.45.perfctr-3.1/drivers/perfctr/Makefile
--- linux-2.5.45/drivers/perfctr/Makefile	Thu Jan  1 01:00:00 1970
+++ linux-2.5.45.perfctr-3.1/drivers/perfctr/Makefile	Thu Oct 31 23:16:59 2002
@@ -0,0 +1,13 @@
+# $Id: Makefile,v 1.11 2002/10/31 22:16:59 mikpe Exp $
+# Makefile for the Performance-monitoring counters driver.
+
+perfctr-objs-y :=
+
+perfctr-objs-$(CONFIG_X86) += x86.o
+
+perfctr-objs-$(CONFIG_PERFCTR_VIRTUAL) += virtual.o
+
+perfctr-objs		:= $(perfctr-objs-y)
+obj-$(CONFIG_PERFCTR)	:= perfctr.o
+
+include $(TOPDIR)/Rules.make

                 reply	other threads:[~2002-10-31 23:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200210312310.AAA07612@kim.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --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