From: akpm@linux-foundation.org
To: linux-ia64@vger.kernel.org
Subject: [patch 2/4] ia64 UV: use LED to indicate CPU is active
Date: Mon, 22 Sep 2008 21:43:37 +0000 [thread overview]
Message-ID: <200809222143.m8MLhcN4031422@imap1.linux-foundation.org> (raw)
From: Mike Travis <travis@sgi.com>
* Add an idle callback to turn on/off a LED indicating that
the CPU is "active" (ON) or "idle" (OFF).
* Introduces a callback for "post-smp_cpus_done" processing
to setup callback.
Note that this is a RAS feature that allows external monitoring of
various cpu state indicators, not just providing "pretty blinking
lights", as the LED state is readable by the system controller.
Signed-off-by: Mike Travis <travis@sgi.com>
Cc: Tony Luck <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/ia64/include/asm/uv/uv_hub.h | 3 +++
arch/ia64/uv/kernel/setup.c | 19 +++++++++++++++++--
2 files changed, 20 insertions(+), 2 deletions(-)
diff -puN arch/ia64/include/asm/uv/uv_hub.h~ia64-uv-use-led-to-indicate-cpu-is-active arch/ia64/include/asm/uv/uv_hub.h
--- a/arch/ia64/include/asm/uv/uv_hub.h~ia64-uv-use-led-to-indicate-cpu-is-active
+++ a/arch/ia64/include/asm/uv/uv_hub.h
@@ -150,6 +150,9 @@ DECLARE_PER_CPU(struct uv_hub_info_s, __
#define LED_CPU_BLINK 0xffff /* blink led */
#define LED_CPU_HB_INTERVAL (HZ/2) /* blink once per second */
+/* idle callback */
+extern void (*ia64_mark_idle) (int);
+
/*
* Macros for converting between kernel virtual addresses, socket local physical
* addresses, and UV global physical addresses.
diff -puN arch/ia64/uv/kernel/setup.c~ia64-uv-use-led-to-indicate-cpu-is-active arch/ia64/uv/kernel/setup.c
--- a/arch/ia64/uv/kernel/setup.c~ia64-uv-use-led-to-indicate-cpu-is-active
+++ a/arch/ia64/uv/kernel/setup.c
@@ -52,6 +52,19 @@ static __init void get_lowmem_redirect(u
BUG();
}
+/*
+ * Illuminate "activity" LED when CPU is going "active",
+ * extinguish when going "idle".
+ */
+static void uv_idle(int state)
+{
+ if (state)
+ uv_set_led_bits(0, LED_CPU_ACTIVITY);
+
+ else
+ uv_set_led_bits(LED_CPU_ACTIVITY, LED_CPU_ACTIVITY);
+}
+
void __init uv_setup(char **cmdline_p)
{
union uvh_si_addr_map_config_u m_n_config;
@@ -104,9 +117,11 @@ void __init uv_setup(char **cmdline_p)
uv_cpu_hub_info(cpu)->gnode_upper = gnode_upper;
uv_cpu_hub_info(cpu)->global_mmr_base = mmr_base;
uv_cpu_hub_info(cpu)->coherency_domain_number = 0;/* ZZZ */
- uv_cpu_hub_info(cpu)->led_offset = LED_LOCAL_MMR_BASE + lcpu;
+ uv_cpu_hub_info(cpu)->led_offset = LED_LOCAL_MMR_BASE + cpu;
uv_cpu_hub_info(cpu)->led_state = 0;
printk(KERN_DEBUG "UV cpu %d, nid %d\n", cpu, nid);
}
-}
+ /* enable idle callback */
+ ia64_mark_idle = &uv_idle;
+}
_
reply other threads:[~2008-09-22 21:43 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=200809222143.m8MLhcN4031422@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-ia64@vger.kernel.org \
/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