From: Arnd Bergmann <arnd@arndb.de>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: bryan.wu@analog.com, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/5] Blackfin: blackfin architecture patch update
Date: Sun, 4 Mar 2007 00:05:37 +0100 [thread overview]
Message-ID: <200703040005.38189.arnd@arndb.de> (raw)
In-Reply-To: <20070303225002.GB28961@outpost.ds9a.nl>
On Saturday 03 March 2007 23:50:02 bert hubert wrote:
> > for (;;)
> > asm volatile ("idle");
>
> This looks remarkably like relax_cpu()
Actually not: cpu_relax() is defined as barrier(), it can't
call idle because that might make it sleep for a indefinite
amount of time (until the next interrupt, but only if they
are enabled).
Some nice architectures provide a hardware mechanism to do
cpu_relax, like going to low-power mode for a few microseconds,
but this one doesn't seem to have it.
Arnd <><
next prev parent reply other threads:[~2007-03-03 23:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 4:14 [PATCH -mm 1/5] Blackfin: blackfin architecture patch update Wu, Bryan
2007-03-03 20:38 ` Arnd Bergmann
2007-03-05 7:13 ` Wu, Bryan
2007-03-03 22:30 ` Arnd Bergmann
2007-03-03 22:50 ` bert hubert
2007-03-03 23:05 ` Arnd Bergmann [this message]
2007-03-05 6:54 ` Aubrey Li
2007-03-05 8:47 ` Arnd Bergmann
2007-03-05 9:19 ` Wu, Bryan
2007-03-05 16:43 ` Arnd Bergmann
2007-03-05 7:34 ` Wu, Bryan
2007-03-05 8:10 ` Arnd Bergmann
2007-03-06 2:09 ` Mike Frysinger
2007-03-05 9:23 ` Paul Mundt
2007-03-05 12:32 ` Bernd Schmidt
2007-03-05 12:39 ` Paul Mundt
2007-03-05 13:26 ` Robin Getz
2007-03-05 14:00 ` Paul Mundt
2007-03-05 16:29 ` Robin Getz
2007-03-05 17:32 ` Paul Mundt
2007-03-05 22:06 ` Robin Getz
2007-03-06 2:04 ` Mike Frysinger
2007-03-21 15:44 ` Mike Frysinger
2007-03-21 23:42 ` Paul Mundt
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=200703040005.38189.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=bert.hubert@netherlabs.nl \
--cc=bryan.wu@analog.com \
--cc=linux-kernel@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 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.