From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH] fsys_gettimeofday leaps days if it runs with nojitter
Date: Fri, 13 Jul 2007 01:27:30 +0000 [thread overview]
Message-ID: <4696D502.7010701@jp.fujitsu.com> (raw)
In-Reply-To: <468CA2D6.40204@jp.fujitsu.com>
Luck, Tony wrote:
>>> I'm guessing here ... I haven't cross-checked with the architects.
>> I'll be glad if we can get a comment from Intel's architects.
>
> I talked this through with an architect, and I'm right. In the
> sequence:
>
> ld4.acq rM = [rN]
> ;;
> mov rP = ar.itc
>
> there are no dependencies, so the read of ar.itc can occur
> "IMMEDIATELY after the load issues".
>
> Consuming the result of the load in between will create a
> dependency ... so the timestamp will be taken as we want it,
> after the load.
>
> So I can apply this patch (moving the "and r28 = ~1,r28").
Thank you for checking it.
> What other time patches are you still pushing? The time
> interpolator changes that were predicted still look like
> they are pending somewhere (kernel/timer.c hasn't been
> changed).
>
> -Tony
I don't know the current status of Bob's patches...
I hope you don't mind applying my small patches before Bob's.
Here are 2 pending patches I'm pushing :
- [PATCH] ia64: Scalability improvement of gettimeofday with
jitter compensation
- [PATCH] fsys_gettimeofday leaps days if it runs with nojitter
I confirmed that these 2 can be applied to 2.6.22 (with some offset).
Let me know if you need refreshed ones.
Thanks,
H.Seto
next prev parent reply other threads:[~2007-07-13 1:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 7:50 [RFC][PATCH] fsys_gettimeofday leaps days if it runs with nojitter Hidetoshi Seto
2007-07-05 8:48 ` Andreas Schwab
2007-07-05 8:57 ` Hidetoshi Seto
2007-07-10 22:20 ` Luck, Tony
2007-07-11 1:31 ` Hidetoshi Seto
2007-07-12 22:33 ` Luck, Tony
2007-07-13 1:27 ` Hidetoshi Seto [this message]
2007-07-13 9:49 ` Bob Picco
2007-07-13 23:25 ` Luck, Tony
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=4696D502.7010701@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.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