From: Zoltan Menyhart <Zoltan.Menyhart_AT_bull.net@nospam.org>
To: linux-ia64@vger.kernel.org
Subject: Re: sched_clock
Date: Fri, 04 Jun 2004 11:11:26 +0000 [thread overview]
Message-ID: <40C058DE.EF547CFB@nospam.org> (raw)
In-Reply-To: <40B4868F.B649611C@nospam.org>
David Mosberger wrote:
>
> Yes, you're right, there is an intermediate-result overflow problem in
> sched_clock() that I missed. How does the attached patch work for you?
Thank you, it is O.K.
On the other hand, we might have similar problems in fsys.S. Some comments
like the one below makes me worry a bit:
// if now < last_tick, set p7 = 1, p8 = 0
I cannot really say that I fully understand what is in fsys.S, but
should not "now" always be after no matter what time stamp, last tick ?
Thanks,
Zoltán
next prev parent reply other threads:[~2004-06-04 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 11:59 sched_clock Zoltan Menyhart
2004-06-03 22:46 ` sched_clock David Mosberger
2004-06-04 9:43 ` sched_clock Ingo Molnar
2004-06-04 11:02 ` sched_clock Andi Kleen
2004-06-04 11:11 ` Zoltan Menyhart [this message]
2004-06-04 22:23 ` sched_clock David Mosberger
2004-06-04 22:52 ` sched_clock David Mosberger
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=40C058DE.EF547CFB@nospam.org \
--to=zoltan.menyhart_at_bull.net@nospam.org \
--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