All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: vikesh rambaran <vikesh.rambaran@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Large (negative) latency test results and fast PC clock
Date: Mon, 07 Jan 2008 10:49:11 +0100	[thread overview]
Message-ID: <4781F597.101@domain.hid> (raw)
In-Reply-To: <b131c9f0801010817l2f36aea3h7d521d7be8b7255@domain.hid>

vikesh rambaran wrote:
> ...
> How does xenomai select the timerdev and the clockdev from the following
> kernel config parameters ?
> 
> a) X86_LOCAL_APIC
> b) X86_IO_APIC
> c) X86_GOOD_APIC
> d) X86_UP_APIC
> e) M586TSC
> f) X86_TSC
> g) HPET

To answer this question (for x86-32 aka i386):

Timer = X86_LOCAL_APIC ? LAPIC : PIT
Clock = X86_TSC ? TSC : PIT-emulated TSC

X86_UP_APIC controls the availability of X86_LOCAL_APIC on UP, M586TSC
(or better) enables X86_TSC. X86_IO_APIC and X86_GOOD_APIC have no
relevance here (the latter just influence the way the APIC is accessed
on i386). HPET_TIMER has that well-known side-effect of blocking the PIT
in case there is actually HPET hardware available and used by Linux.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


      parent reply	other threads:[~2008-01-07  9:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-30 12:11 [Xenomai-help] Large (negative) latency test results and fast PC clock vikesh rambaran
2007-12-30 23:16 ` Jan Kiszka
     [not found] ` <200712310033.05927.paul_c@domain.hid>
2007-12-31 14:04   ` vikesh rambaran
2007-12-31 14:43     ` Jan Kiszka
2007-12-31 15:54       ` vikesh rambaran
2007-12-31 16:54         ` Paul
2008-01-01 16:17           ` vikesh rambaran
2008-01-01 19:48             ` Paul
2008-01-04 12:39               ` vikesh rambaran
2008-01-04 16:26                 ` Paul
2008-01-07 10:35                   ` vikesh rambaran
2008-01-07 11:30                     ` vikesh rambaran
2008-01-07  9:49             ` Jan Kiszka [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=4781F597.101@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=vikesh.rambaran@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.