From: timur@tabi.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Convert PowerPC macro spin_event_timeout() to architecture independent macro
Date: Wed, 31 Jul 2013 19:20:29 -0500 [thread overview]
Message-ID: <51F9A9CD.1040804@tabi.org> (raw)
In-Reply-To: <51F9A8F1.9020704@codeaurora.org>
On 07/31/2013 07:16 PM, Stephen Boyd wrote:
> cpu_relax() is usually just a compiler barrier or an instruction hint to
> the cpu that it should cool down because we're spinning in a tight loop.
> It certainly shouldn't be calling into the scheduler.
Ah yes, I remember now. So it does seem that if we can fix the problem
of non-incrementing 'jiffies', then this macro can be used in interrupts.
Of course, that assumes that spinning in interrupt context is a good
idea to begin with. Maybe we shouldn't be encouraging it?
>> > FYI, you might want to look at the code reviews for spin_event_timeout()
>> > on the linuxppc-dev mailing list, back in March 2009.
>> >
> Sure. Any pointers? Otherwise I'll go digging around the archives.
https://lists.ozlabs.org/pipermail/linuxppc-dev/2009-March/thread.html
--
Timur Tabi
next prev parent reply other threads:[~2013-08-01 0:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 12:38 [PATCH 0/2] Make PPC macro spin_event_timeout() architecture independent Arpit Goel
2013-07-30 12:38 ` [PATCH 1/2] Make USECS_PER_JIFFY available for generic use Arpit Goel
2013-07-30 12:38 ` [PATCH 2/2] Convert PowerPC macro spin_event_timeout() to architecture independent macro Arpit Goel
2013-07-31 7:16 ` Stephen Boyd
2013-07-31 23:44 ` Timur Tabi
2013-08-01 0:04 ` Stephen Boyd
2013-08-01 0:13 ` Timur Tabi
2013-08-01 0:16 ` Stephen Boyd
2013-08-01 0:20 ` Timur Tabi [this message]
2013-08-01 1:36 ` Stephen Boyd
2013-08-01 6:27 ` Srivastava Rajan-B34330
2013-08-01 9:26 ` Goel Arpit-B44344
2013-08-01 0:02 ` Timur Tabi
2013-08-01 4:38 ` Goel Arpit-B44344
2013-08-01 4:43 ` Timur Tabi
2013-07-30 13:08 ` [PATCH 0/2] Make PPC macro spin_event_timeout() architecture independent Geert Uytterhoeven
2013-07-31 11:09 ` Goel Arpit-B44344
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=51F9A9CD.1040804@tabi.org \
--to=timur@tabi.org \
--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).