From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] tcb_clksrc: Use 32 bit tcb as sched_clock
Date: Mon, 23 Jan 2017 14:59:42 +0100 [thread overview]
Message-ID: <20170123135942.GC2166@mai> (raw)
In-Reply-To: <20170111135059.21318-1-david.engraf@sysgo.com>
On Wed, Jan 11, 2017 at 02:50:59PM +0100, David Engraf wrote:
> On newer boards the TC can be read as single 32 bit value without locking.
> Thus the clock can be used as reference for sched_clock which is much more
> accurate than the jiffies implementation.
>
> Tested on a Atmel SAMA5D2 board.
>
> Signed-off-by: David Engraf <david.engraf@sysgo.com>
> ---
Nicolas,
if you agree I will take this change.
-- Daniel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: David Engraf <david.engraf@sysgo.com>
Cc: nicolas.ferre@atmel.com, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tcb_clksrc: Use 32 bit tcb as sched_clock
Date: Mon, 23 Jan 2017 14:59:42 +0100 [thread overview]
Message-ID: <20170123135942.GC2166@mai> (raw)
In-Reply-To: <20170111135059.21318-1-david.engraf@sysgo.com>
On Wed, Jan 11, 2017 at 02:50:59PM +0100, David Engraf wrote:
> On newer boards the TC can be read as single 32 bit value without locking.
> Thus the clock can be used as reference for sched_clock which is much more
> accurate than the jiffies implementation.
>
> Tested on a Atmel SAMA5D2 board.
>
> Signed-off-by: David Engraf <david.engraf@sysgo.com>
> ---
Nicolas,
if you agree I will take this change.
-- Daniel
next prev parent reply other threads:[~2017-01-23 13:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 13:50 [PATCH] tcb_clksrc: Use 32 bit tcb as sched_clock David Engraf
2017-01-11 13:50 ` David Engraf
2017-01-17 9:13 ` Daniel Lezcano
2017-01-17 9:29 ` David Engraf
2017-01-17 9:29 ` David Engraf
2017-01-17 9:42 ` Mason
2017-01-17 9:42 ` Mason
2017-01-17 14:44 ` Romain Izard
2017-01-23 13:59 ` Daniel Lezcano [this message]
2017-01-23 13:59 ` Daniel Lezcano
2017-01-24 13:39 ` Nicolas Ferre
2017-01-24 13:39 ` Nicolas Ferre
2017-01-24 13:39 ` Nicolas Ferre
2017-01-24 13:39 ` Nicolas Ferre
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=20170123135942.GC2166@mai \
--to=daniel.lezcano@linaro.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 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.