From: Anders Blomdell <anders.blomdell@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] some results on my laptop
Date: Fri, 03 Feb 2006 10:14:08 +0100 [thread overview]
Message-ID: <43E31EE0.8020808@domain.hid> (raw)
In-Reply-To: <43E31186.1000007@domain.hid>
Jan Kiszka wrote:
> ...and may also add further latencies with the system has to speed up
> again. Anyway, there might be use-cases where power consumption is -
> besides latency - also an important issue. I'm just thinking of our
> smaller mobile robots where the power demand of the drives and the
> controller are not that far apart as on the larger platforms.
>
> What about other time sources on x86? Which systems already have HPET
> these days, and does this source not suffer from frequency scaling? I
> once read that HPET is quite easy to program, is this true? IOW, would
> it be worth considering to add this to the HAL?
If it an computer with ACPI (which is very likely), one could use the PM Timer
(3.579545 MHz) as the base system clock, and sync with TSC at every clockscaling
and power events (the reason for that is that PM Timer reads are quite slow
(around 1 microsecond on the hardwares I have tested), so most timer stuff
should go via TSC).
The advantage with this is that the system will keep accurate time even in the
low power modes (when TSC is turned off). I have done a crude implementation of
this on KURT (http://www.ittc.ku.edu/kurt/), and it is a workable solution
There are also good research/development oppurtunities in:
1. scheduling ACPI wakeup from those low-power modes in such good
time that all realtime requirements are met :-)
2. scheduling of clockscaling changes to make minimum impact
on realtime tasks
(For ACPI, see http://www.acpi.info/DOWNLOADS/ACPIspec30a.pdf)
--
Regards
Anders Blomdell
next prev parent reply other threads:[~2006-02-03 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 22:33 [Xenomai-core] some results on my laptop Jim Cromie
2006-02-02 22:59 ` Philippe Gerum
2006-02-03 0:26 ` Jim Cromie
2006-02-03 7:51 ` Philippe Gerum
2006-02-03 8:17 ` Jan Kiszka
2006-02-03 8:26 ` Jan Kiszka
2006-02-03 8:58 ` Philippe Gerum
2006-02-03 9:18 ` Anders Blomdell
2006-02-03 9:26 ` Jan Kiszka
2006-02-03 9:14 ` Anders Blomdell [this message]
2006-02-03 9:35 ` Jan Kiszka
2006-02-03 10:01 ` Anders Blomdell
2006-02-03 10:20 ` Jan Kiszka
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=43E31EE0.8020808@domain.hid \
--to=anders.blomdell@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=xenomai@xenomai.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.