From: Mike Travis <travis@sgi.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Jack Steiner <steiner@sgi.com>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 3/6] x86_64 UV: Use blinking LED for heartbeat display
Date: Tue, 26 Aug 2008 13:53:48 -0700 [thread overview]
Message-ID: <48B46D5C.5020504@sgi.com> (raw)
In-Reply-To: <20080813095715.GB27074@atrey.karlin.mff.cuni.cz>
Pavel Machek wrote:
>> * Mike Travis <travis@sgi.com> wrote:
>>
>>> +#ifdef CONFIG_CLOCKSOURCE_WATCHDOG
>>> +static void uv_display_heartbeat(void)
>>> +{
>>> + int cpu;
>>> +
>>> + uv_hub_info->led_heartbeat_count = nr_cpu_ids;
>>> +
>>> + for_each_online_cpu(cpu) {
>>> + struct uv_hub_info_s *hub = uv_cpu_hub_info(cpu);
>>> +
>>> + if (hub->led_heartbeat_count > 0) {
>>> + uv_set_led_bits_on(cpu, LED_CPU_BLINK,
>>> + LED_CPU_HEARTBEAT);
>>> + --hub->led_heartbeat_count;
>>> + }
>> this too is a bad idea. Imagine 16K cores and assume that each such
>> iteration takes a few usecs (we write cross CPU) and you've got a
>> GHz-ish CPU. That can easily be _milliseconds_ of delay (or more) - and
>> in a function (the clocksource watchdog) that is all about precise
>> timings.
>>
>> It is also very non-preemptable.
>
> LED subsystem already has nice heartbeat trigger.
> Pavel
>From Documentation/leds-class.txt:
Future Development
==================
At the moment, a trigger can't be created specifically for a single LED.
There are a number of cases where a trigger might only be mappable to a
particular LED (ACPI?). The addition of triggers provided by the LED driver
should cover this option and be possible to add without breaking the
current interface.
--
The SGI system has a set of leds per cpu, and the goal is that the leds
display heartbeat and "idle-ness" information specific to that cpu. At
first glance I don't see this capability in the LED subsystem. Am I
missing something?
Additionally, the 8 leds are written as one byte with each led being
full on or full off. It seems to be a big overhead to support the led
class since I'd have to kluge together some means of sharing the current
led register value [we really don't want to have to read the current reg
value before updating a single led.]
But I will definitely look at the led_heartbeat_function more closely.
Any advice gladly welcomed!
Thanks!
Mike
next prev parent reply other threads:[~2008-08-26 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 0:56 [PATCH 0/6] SGI UV: Provide a LED driver and some System Activity Indicators Mike Travis
2008-08-08 0:56 ` [PATCH 1/6] x86_64 UV: Provide a LED driver for UV Systems Mike Travis
2008-08-08 0:56 ` [PATCH 2/6] x86_64 UV: Use LED to indicate CPU is active Mike Travis
2008-08-11 15:53 ` Ingo Molnar
2008-08-13 9:56 ` Pavel Machek
2008-08-25 17:53 ` Mike Travis
2008-08-25 17:49 ` Mike Travis
2008-08-08 0:56 ` [PATCH 3/6] x86_64 UV: Use blinking LED for heartbeat display Mike Travis
2008-08-11 16:02 ` Ingo Molnar
2008-08-13 9:57 ` Pavel Machek
2008-08-26 20:53 ` Mike Travis [this message]
2008-08-27 21:38 ` Pavel Machek
2008-08-25 17:55 ` Mike Travis
2008-08-08 0:56 ` [PATCH 4/6] ia64 UV: Provide a LED driver for UV Systems Mike Travis
2008-08-08 6:07 ` Andrew Morton
2008-08-08 0:56 ` [PATCH 5/6] ia64 UV: Use LED to indicate CPU is active Mike Travis
2008-08-08 0:56 ` [PATCH 6/6] ia64 UV: Use blinking LED for heartbeat display Mike Travis
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=48B46D5C.5020504@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.