From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arch/arm/kernel: use cpu_relax() in halt loops
Date: Tue, 14 Dec 2010 22:51:26 +0000 [thread overview]
Message-ID: <20101214225126.GD24303@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20101214224848.GA1706@debian.debian>
On Tue, Dec 14, 2010 at 11:48:48PM +0100, Jonathan Neusch?fer wrote:
> Looking throught arch/arm/kernel/ I found some halt loops.
> I just thought we could save some power here using cpu_relax(),
> or am I missing something?
#if __LINUX_ARM_ARCH__ == 6
#define cpu_relax() smp_mb()
#else
#define cpu_relax() barrier()
#endif
IOW, it's either a memory barrier or compiler barrier on ARM; it
doesn't do any power saving.
next prev parent reply other threads:[~2010-12-14 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 22:48 [PATCH] arch/arm/kernel: use cpu_relax() in halt loops Jonathan Neuschäfer
2010-12-14 22:51 ` Russell King - ARM Linux [this message]
2010-12-14 23:00 ` Jonathan Neuschäfer
-- strict thread matches above, loose matches on Subject: below --
2010-11-27 20:20 Jonathan Neuschäfer
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=20101214225126.GD24303@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;
as well as URLs for NNTP newsgroup(s).