From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: setitimer shows different between amd64 and ia32
Date: Mon, 25 Jul 2011 04:06:13 +0000 [thread overview]
Message-ID: <CAGdaadbmDSZD30yuRe+tnT9OAz=JTRrkztEv9F4eLiLhBa7nDw@mail.gmail.com> (raw)
In-Reply-To: <20110725031038.GA11399@adam-laptop>
Hi....
On Mon, Jul 25, 2011 at 03:10, Adam Lee <adam8157@gmail.com> wrote:
> Hi, all
>
> I'm working on a test which invoking setitimer(), and it hang in
> ia32 and ppc, but passed in amd64, could you guys give some help?
>
> 1, I know the 'value.it_interval.tv_usec' is too short, but why amd64
> passed?
All of my answers are pure speculation. Regarding AMD64 that
successfully run the code, I am not sure it's due to the processor
itself. Maybe because...in your machine that use AMD64, it uses HPET
by default?
> 2, If I switch clock source from "tsc" to "hpet" on ia32, it passed.
This is interesting. I can only offer one explanation: finer grained
timer resolution. TSC itself should be fast, but I am not whether it
triggers interrupt...while on the other hand HPET will deliver
interrupt.
> 3, I compiled it in ia32 and run it with ia32-libs in amd64, it passed.
Very confusing to me. Again I can only guess that maybe in your AMD64
machine, HPET is default timer?
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-07-25 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 3:10 setitimer shows different between amd64 and ia32 Adam Lee
2011-07-25 4:06 ` Mulyadi Santosa [this message]
2011-07-25 4:09 ` Dave Hylands
2011-07-25 6:51 ` Adam Lee
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='CAGdaadbmDSZD30yuRe+tnT9OAz=JTRrkztEv9F4eLiLhBa7nDw@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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.