All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] i8253 clocksource vs. rthal_get_8254_tsc
Date: Wed, 06 Feb 2013 13:30:29 +0100	[thread overview]
Message-ID: <51124CE5.7030906@siemens.com> (raw)
In-Reply-To: <51124C88.1060401@siemens.com>

On 2013-02-06 13:28, Jan Kiszka wrote:
> On 2013-02-06 13:18, Gilles Chanteperdrix wrote:
>> On 02/06/2013 11:20 AM, Jan Kiszka wrote:
>>
>>> Hi Gilles,
>>>
>>> I just realized that there is now a 8253 clocksource in core-3.4+. How
>>> does this work together with Xenomai's TSC emulation via the 8254 in the
>>> x86 hal_32? Xenomai reprograms the PIT in rthal_setup_8254_tsc - is this
>>> harmless?
>>>
>>> I came across this while trying to get rid of Xenomai's "depends on
>>> !INPUT_PCSPKR" to avoid that circular Kbuild dependency.
>>
>>
>> This emulation replaces Xenomai's TSC emulation when the kernel boots on
>> a cpu without a TSC: the detection is made at run-time instead of
>> compilation time using self-modifying code (this in order to be able to
>> build Debian kernels which boots with any configuration).
> 
> Hmm, that's for the kernel. But what prevents rthal_setup_8254_tsc from
> being executed in addition? I'm currently a bit lost in the #ifdefs.

Ah! IPIPE_CORE_APIREV < 2, right?

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux


  reply	other threads:[~2013-02-06 12:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 10:20 [Xenomai] i8253 clocksource vs. rthal_get_8254_tsc Jan Kiszka
2013-02-06 12:18 ` Gilles Chanteperdrix
2013-02-06 12:28   ` Jan Kiszka
2013-02-06 12:30     ` Jan Kiszka [this message]
2013-02-06 12:31     ` Gilles Chanteperdrix
2013-02-06 12:33       ` Jan Kiszka
2013-02-06 12:36         ` Gilles Chanteperdrix
2013-02-06 12:43           ` 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=51124CE5.7030906@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.