From: Ray Bryant <raybry@sgi.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Hanna Linder <hannal@us.ibm.com>,
"Martin J. Bligh" <mbligh@aracnet.com>,
lse-tech@lists.sourceforge.net, linux-mm@kvack.org
Subject: lockmeter on ia64
Date: Wed, 17 Dec 2003 01:08:45 -0600 [thread overview]
Message-ID: <3FE000FD.2090408@sgi.com> (raw)
Andrew,
It looks like the 2.6.0 lockmeter patch has lost the configuration menu entry to
enable lockmeter on ia64. This is true of both 2.6.0-test10-mm1 and
2.6.0-test11-mjb3. (Martin appears to pull this from your tree.) Below is
the trivial patch to fix this. With this change it appears to work fine on
Altix, at least.
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1520 -> 1.1521
# arch/ia64/Kconfig 1.49 -> 1.50
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/12/16 raybry@tomahawk.engr.sgi.com 1.1521
# Add missing menu item for Lockmeter in arch/ia64/Kconfig
# --------------------------------------------
#
diff -Nru a/arch/ia64/Kconfig b/arch/ia64/Kconfig
--- a/arch/ia64/Kconfig Tue Dec 16 16:44:00 2003
+++ b/arch/ia64/Kconfig Tue Dec 16 16:44:00 2003
@@ -686,6 +686,13 @@
debugging info resulting in a larger kernel image.
Say Y here only if you plan to use gdb to debug the kernel.
If you don't debug the kernel, you can say N.
+
+config LOCKMETER
+ bool "Kernel lock metering"
+ depends on SMP
+ help
+ Say Y to enable kernel lock metering, which adds overhead to SMP locks,
+ but allows you to see various statistics using the lockstat command.
endmenu
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2003-12-17 7:08 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=3FE000FD.2090408@sgi.com \
--to=raybry@sgi.com \
--cc=akpm@digeo.com \
--cc=hannal@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.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