From: Daniel Laird <danieljlaird@hotmail.com>
To: linux-mips@linux-mips.org
Subject: Re: 2.6.19 timer API changes
Date: Wed, 20 Dec 2006 07:46:24 -0800 (PST) [thread overview]
Message-ID: <7992266.post@talk.nabble.com> (raw)
In-Reply-To: <20061221.002420.132303561.anemo@mba.ocn.ne.jp>
hello,
Atsushi Nemoto wrote:
>
> On Wed, 20 Dec 2006 01:37:17 -0800 (PST), Daniel Laird
> <danieljlaird@hotmail.com> wrote:
>> Then I get a normal startup. i.e it boots fast (no 10second hang). If
>> I
>> remove the write_c0_count then I get the 10 second hang.
>
> I think Kevin's analysis about this 10 second hang is correct. Then I
> think my last patch will work as well.
>
>> I have no idea if gettimeofday is broken. ANy ideas on testing this? Is
>> there a test package / application that will do this? Before I write my
>> own
>
> Calling gettimeofday() continuously many times (at least some tick
> periods) and calculates times between each call. Those differences
> should be almost same. Of course you must run this program on very
> idle system (or you must raise its priority).
>
> ---
> Atsushi Nemoto
>
Thanks guys I can see how Kevin has come to his conclusion (On 10 secs And I
think I agree)!
I will try your 2nd proposed solution, I gave it a very quick go but it did
not work. I will give this some proper time, I think some mips_clocksource
needed to be externed etc. (and add linux/clocksource.h ) to
pnx8550/common/time.c.
Hopefullly this will make it compile, and then I can trace the problem a bit
more. It might be after Christmas though before I come back to this
Again cheers for the help.
Dan
--
View this message in context: http://www.nabble.com/2.6.19-timer-API-changes-tf2838715.html#a7992266
Sent from the linux-mips main mailing list archive at Nabble.com.
next prev parent reply other threads:[~2006-12-20 15:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 9:15 2.6.19 timer API changes Daniel Laird
2006-12-19 8:17 ` Daniel Laird
2006-12-19 14:34 ` Atsushi Nemoto
2006-12-19 14:51 ` Daniel Laird
2006-12-19 16:23 ` Sergei Shtylyov
2006-12-19 15:01 ` Atsushi Nemoto
2006-12-19 15:34 ` Daniel Laird
2006-12-19 17:15 ` Atsushi Nemoto
2006-12-20 9:37 ` Daniel Laird
2006-12-20 14:12 ` Sergei Shtylyov
2006-12-20 14:50 ` Kevin D. Kissell
2006-12-20 14:50 ` Kevin D. Kissell
2006-12-20 18:01 ` Sergei Shtylyov
2006-12-20 15:24 ` Atsushi Nemoto
2006-12-20 15:46 ` Daniel Laird [this message]
2006-12-20 14:29 ` Sergei Shtylyov
2006-12-20 15:40 ` Atsushi Nemoto
2006-12-20 15:48 ` Daniel Laird
2006-12-20 15:48 ` Sergei Shtylyov
2006-12-19 15:52 ` Sergei Shtylyov
2006-12-19 16:29 ` Atsushi Nemoto
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=7992266.post@talk.nabble.com \
--to=danieljlaird@hotmail.com \
--cc=linux-mips@linux-mips.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