From: Raz <raziebe@gmail.com>
To: "Lee Revell" <rlrevell@joe-job.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: mmap over HPET - 32 bit wrap arround
Date: Sat, 31 May 2008 21:20:55 +0300 [thread overview]
Message-ID: <5d96567b0805311120w516b0064h55a211c707a1dbae@mail.gmail.com> (raw)
In-Reply-To: <75b66ecd0805281657k7b988bf1qa46e806810da0c17@mail.gmail.com>
On Thu, May 29, 2008 at 2:57 AM, Lee Revell <rlrevell@joe-job.com> wrote:
> On Wed, May 28, 2008 at 6:19 PM, Raz <raziebe@gmail.com> wrote:
>> I am wondering wether someone can explain how hpet behaves. The bellow
>> is a short program that reads from a mmaped /dev/hpet the time. I am
>> running it and it looks that afer ~296 seconds the counter resets . I
>> AM RUNNING 64bi KERNEL(2.6.18-8.el5) and reading a 64BIT VARIABLE.
>> my hpet is 14MHZ, so I am guessing a 32bit wraparound ( ~296 * 14Mhz
>> ) = MAX_INT . but why ?
>>
>
> HPET counter can be either 32 or 64 bit. Check COUNT_SIZE_CAP.
>
> http://www.intel.com/hardwaredesign/hpetspec_1.pdf
>
> Lee
>
Thank you Lee for your response. According to the SPEC I debugged and found:
section :2.3.4 Main Capabilities and ID Register
bit 13: HPET_COUNTER_SIZE_MASK & readq(&hpet->hpet_cap) is on.
indicates 64bit timer.
section 2.4.8 Timer n Configuration and Capabilties Register
bit 5 on Tn_SIZE_CAP is to 32bit. Problem is that it is readonly( page
18 in spec).
None of the above counters is 64bit, and there is no BIOS settings for
hpet ( T61 Lenovo ).
Furthermore , I have 3 timers , and only a single /dev/hpet. why ?
thank you
--
Raz
prev parent reply other threads:[~2008-05-31 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83CA05F64804AF43B8F733C4ABDFAA5101384F73@mail1.bitband.com>
[not found] ` <83CA05F64804AF43B8F733C4ABDFAA5101384FA4@mail1.bitband.com>
2008-05-28 22:19 ` Raz
2008-05-28 23:57 ` Lee Revell
2008-05-31 18:20 ` Raz [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=5d96567b0805311120w516b0064h55a211c707a1dbae@mail.gmail.com \
--to=raziebe@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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
all inboxes | Powered by JetHome®