From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: Sven Zenker <Sven.Zenker@gmx.net>, "Jim C. Brown" <jma5@umd.edu>
Cc: qemu-devel@nongnu.org
Subject: Re: Re: [Qemu-devel] Timing problems
Date: Wed, 31 Aug 2005 19:19:02 +0700 [thread overview]
Message-ID: <200508311919.02083.a_mulyadi@softhome.net> (raw)
In-Reply-To: <1125436100.9706.19.camel@linux>
Hello Sven...
> rdtsc gives you the cpu's clock count, which, if CPU frequency
> changes, or your code is run on different processors (multiprocessor
> machine), cannot be assumed to be related to real time anymore.
> Resolutionwise, the real time clock may be inferior, of course, as
> Jim mentioned. Jim: could you point me to this other patch? Thanks!
Oh, so sorry, I was mistakenly made conclusion about your patch. yes,
you are correct, get_clock() will do the trick....while rdtsc won't
work because the clock will run vary during speed-stepping....
The unified format of diff looks great! :)
regards
Mulyadi
prev parent reply other threads:[~2005-08-31 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 19:23 [Qemu-devel] Timing problems Sven Zenker
2005-08-29 3:01 ` Mulyadi Santosa
2005-08-29 3:21 ` Jim C. Brown
2005-08-30 21:08 ` Sven Zenker
2005-08-31 12:19 ` Mulyadi Santosa [this message]
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=200508311919.02083.a_mulyadi@softhome.net \
--to=a_mulyadi@softhome.net \
--cc=Sven.Zenker@gmx.net \
--cc=jma5@umd.edu \
--cc=qemu-devel@nongnu.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.