From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Simon Glass <sjg@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 0/3] Add accurate boot timing to a Linux system
Date: Sat, 24 Sep 2011 09:32:03 +0100 [thread overview]
Message-ID: <20110924083203.GZ17169@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1316818998-30711-1-git-send-email-sjg@chromium.org>
On Fri, Sep 23, 2011 at 04:03:15PM -0700, Simon Glass wrote:
> An accurate timer is required to make the numbers meaningful. Many
> modern platforms have a microsecond timer. This patch set uses a
> function called timer_get_us() to read the timer.
Not another 'get a time value' function. Why do we need soo many?
We have - at least:
ktime_get (and various flavours of it)
do_gettimeofday
getnstimeofday
sched_clock
Do we really need yet another one which will have to be multiplexed
amongst platforms, requiring scaling and so forth from whatever the
platform provides?
Remember that ARM timers are virtually all MMIO mapped, which means
they don't work during early kernel bringup when the MMU mappings for
the hardware have not been setup. (That's the reason stuff like
sched_clock for printk doesn't work early.) That can't be solved by
creating yet another per-platform method to get microseconds.
next prev parent reply other threads:[~2011-09-24 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 23:03 Simon Glass
2011-09-23 23:03 ` [RFC PATCH 1/3] bootstage: Add bootstages to record timing in the kernel Simon Glass
2011-09-23 23:03 ` [RFC PATCH 2/3] bootstage: Insert bootstage_mark to record timing for bootup Simon Glass
2011-09-25 12:59 ` Bjorn Helgaas
2011-09-23 23:03 ` [RFC PATCH 3/3] bootstage: Get u-boot timing from the device tree Simon Glass
2011-09-23 23:34 ` [RFC PATCH 0/3] Add accurate boot timing to a Linux system Valdis.Kletnieks
2011-09-24 4:10 ` Simon Glass
2011-09-24 8:32 ` Russell King - ARM Linux [this message]
2011-09-24 14:06 ` Simon Glass
2011-09-26 7:53 ` Matthieu CASTET
2011-09-27 18:29 ` Simon Glass
2011-09-25 12:54 ` Bjorn Helgaas
2011-09-27 18:26 ` Simon Glass
2011-09-27 17:56 ` Tim Bird
2011-09-27 17:57 ` Tim Bird
2011-09-27 18:42 ` Simon Glass
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=20110924083203.GZ17169@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjg@chromium.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
all inboxes | Powered by JetHome®