From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: update show_interrupts for online cpu's only
Date: Sat, 31 Jul 2010 15:36:27 +0100 [thread overview]
Message-ID: <20100731143627.GC27064@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1280585333-4870-1-git-send-email-santosh.shilimkar@ti.com>
On Sat, Jul 31, 2010 at 07:38:53PM +0530, Santosh Shilimkar wrote:
> Even after CPUx is logically offline, it's interrupt are displayed
> in proc entry
>
> This patch fixes the same by use of 'for_each_online_cpu' instead
> of 'for_each_present_cpu' in 'show_interrupts' function
What's the synchronisation mechanism between CPUs being brought on or
offline and this file being read?
I believe we have a more dynamic approach to CPU hotplug (using it for
dynamic power saving) than x86, so I believe hotplug events can happen
more often on ARM.
next prev parent reply other threads:[~2010-07-31 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-31 14:08 [PATCH] ARM: update show_interrupts for online cpu's only Santosh Shilimkar
2010-07-31 14:36 ` Russell King - ARM Linux [this message]
2010-07-31 14:48 ` Shilimkar, Santosh
2010-07-31 15:05 ` Russell King - ARM Linux
2010-07-31 15:18 ` Shilimkar, Santosh
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=20100731143627.GC27064@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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