From: Timur Tabi <timur@tabi.org>
To: Goel Arpit-B44344 <B44344@freescale.com>
Cc: "linux-m32r-ja@ml.linux-m32r.org"
<linux-m32r-ja@ml.linux-m32r.org>,
"linux-m68k@vger.kernel.org" <linux-m68k@vger.kernel.org>,
"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
"sam@ravnborg.org" <sam@ravnborg.org>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"jesper.nilsson@axis.com" <jesper.nilsson@axis.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"takata@linux-m32r.org" <takata@linux-m32r.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
Rob Herring <rob.herring@calxeda.com>,
"john.stultz@linaro.org" <john.stultz@linaro.org>,
Stephen Warren <swarren@nvidia.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-m32r@ml.linux-m32r.org" <linux-m32r@ml.linux-m32r.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxf>
Subject: Re: [PATCH 2/2] Convert PowerPC macro spin_event_timeout() to architecture independent macro
Date: Wed, 31 Jul 2013 23:43:18 -0500 [thread overview]
Message-ID: <51F9E766.604@tabi.org> (raw)
In-Reply-To: <0DFB48290CDB0C4680160EBE62E8F9A809E9A2E0@039-SN2MPN1-023.039d.mgd.msft.net>
Goel Arpit-B44344 wrote:
> PowerPC uses hardware timer registers provided by PowerPC architecture to implement spin_event_timeout(). These registers make
> PowerPC implementation of spin_event_timeout() more granular in comparison to ones using generic USECS_PER_JIFFY framework. This
> would handle those cases more granularly in which evaluation of "condition" is taking time or fails.
LOL, it seems I forgot how my own code works. Thanks for the reminder.
For some reason, I thought the PowerPC version was also using
'jiffies'. The concern about using 'jiffies' makes a lot more sense now.
Almost every architecture has a timebase counter. Wouldn't it make more
sense to port tb_ticks_per_usec, get_tbl(), and tb_ticks_since() to
other architectures instead? I don't think 'jiffies' is granular enough
for spin_event_timeout().
WARNING: multiple messages have this Message-ID (diff)
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 23:43:18 -0500 [thread overview]
Message-ID: <51F9E766.604@tabi.org> (raw)
In-Reply-To: <0DFB48290CDB0C4680160EBE62E8F9A809E9A2E0@039-SN2MPN1-023.039d.mgd.msft.net>
Goel Arpit-B44344 wrote:
> PowerPC uses hardware timer registers provided by PowerPC architecture to implement spin_event_timeout(). These registers make
> PowerPC implementation of spin_event_timeout() more granular in comparison to ones using generic USECS_PER_JIFFY framework. This
> would handle those cases more granularly in which evaluation of "condition" is taking time or fails.
LOL, it seems I forgot how my own code works. Thanks for the reminder.
For some reason, I thought the PowerPC version was also using
'jiffies'. The concern about using 'jiffies' makes a lot more sense now.
Almost every architecture has a timebase counter. Wouldn't it make more
sense to port tb_ticks_per_usec, get_tbl(), and tb_ticks_since() to
other architectures instead? I don't think 'jiffies' is granular enough
for spin_event_timeout().
next prev parent reply other threads:[~2013-08-01 4:43 UTC|newest]
Thread overview: 51+ 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:50 ` Arpit Goel
2013-07-30 12:38 ` Arpit Goel
2013-07-30 12:38 ` Arpit Goel
2013-07-30 12:38 ` [PATCH 1/2] Make USECS_PER_JIFFY available for generic use Arpit Goel
2013-07-30 12:50 ` Arpit Goel
2013-07-30 12:38 ` Arpit Goel
2013-07-30 12:38 ` Arpit Goel
2013-07-30 12:38 ` [PATCH 2/2] Convert PowerPC macro spin_event_timeout() to architecture independent macro Arpit Goel
2013-07-30 12:50 ` Arpit Goel
2013-07-30 12:38 ` Arpit Goel
2013-07-30 12:38 ` Arpit Goel
2013-07-31 7:16 ` Stephen Boyd
2013-07-31 7:16 ` Stephen Boyd
2013-07-31 7:16 ` Stephen Boyd
2013-07-31 23:44 ` Timur Tabi
2013-07-31 23:44 ` Timur Tabi
2013-07-31 23:44 ` Timur Tabi
2013-07-31 23:44 ` Timur Tabi
2013-08-01 0:04 ` Stephen Boyd
2013-08-01 0:04 ` Stephen Boyd
2013-08-01 0:04 ` Stephen Boyd
2013-08-01 0:13 ` Timur Tabi
2013-08-01 0:13 ` Timur Tabi
2013-08-01 0:13 ` Timur Tabi
2013-08-01 0:16 ` Stephen Boyd
2013-08-01 0:16 ` Stephen Boyd
2013-08-01 0:16 ` Stephen Boyd
2013-08-01 0:20 ` Timur Tabi
2013-08-01 0:20 ` Timur Tabi
2013-08-01 0:20 ` Timur Tabi
2013-08-01 1:36 ` Stephen Boyd
2013-08-01 1:36 ` Stephen Boyd
2013-08-01 1:36 ` Stephen Boyd
2013-08-01 6:27 ` Srivastava Rajan-B34330
2013-08-01 6:27 ` Srivastava Rajan-B34330
2013-08-01 9:26 ` Goel Arpit-B44344
2013-08-01 9:26 ` Goel Arpit-B44344
2013-08-01 0:02 ` Timur Tabi
2013-08-01 0:02 ` Timur Tabi
2013-08-01 0:02 ` Timur Tabi
2013-08-01 4:38 ` Goel Arpit-B44344
2013-08-01 4:38 ` Goel Arpit-B44344
2013-08-01 4:43 ` Timur Tabi [this message]
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-30 13:08 ` Geert Uytterhoeven
2013-07-30 13:08 ` Geert Uytterhoeven
2013-07-30 13:08 ` Geert Uytterhoeven
2013-07-31 11:09 ` Goel Arpit-B44344
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=51F9E766.604@tabi.org \
--to=timur@tabi.org \
--cc=B44344@freescale.com \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxf \
--cc=heiko.carstens@de.ibm.com \
--cc=jesper.nilsson@axis.com \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-m32r-ja@ml.linux-m32r.org \
--cc=linux-m32r@ml.linux-m32r.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=swarren@nvidia.com \
--cc=takata@linux-m32r.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.