All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] XNARCH_TIMER_IRQ
Date: Thu, 03 Jan 2013 18:34:44 +0100	[thread overview]
Message-ID: <50E5C134.3010804@xenomai.org> (raw)
In-Reply-To: <50E5BF03.5020004@siemens.com>

On 01/03/2013 06:25 PM, Jan Kiszka wrote:
> On 2013-01-03 17:27, Philippe Gerum wrote:
>> On 01/03/2013 04:44 PM, Jan Kiszka wrote:
>>> On 2013-01-03 16:16, Gilles Chanteperdrix wrote:
>>>> On 01/02/2013 06:43 PM, Jan Kiszka wrote:
>>>>> Hi,
>>>>>
>>>>> this may involve some refactoring of the HAL and a bit of I-pipe, so I
>>>>> better ask first:
>>>>>
>>>>> Not sure when it changed, but XNARCH_TIMER_IRQ may no longer return the
>>>>> same values when called on different CPUs. Therefore, It should rather
>>>>> be called XNARCH_THIS_CPU_TIMER_IRQ now.
>>>>>
>>>>> Looking at its users (an I-pipe debug warning pointed it out), there are
>>>>> two that don't expect this: xnintr_query_next() and format_irq_proc().
>>>>> The former actually wants XNARCH_TIMER_IRQ(cpu), the latter needs
>>>>> something like is_timer_irq_on_any_cpus(irq).
>>>>>
>>>>> So I would propose to refactor XNARCH_TIMER_IRQ and RTHAL_TIMER_IRQ
>>>>> accordingly. But this unfortunately requires extensions of I-pipe to
>>>>> provide something like __ipipe_hrtimer_irq(cpu) and
>>>>> __ipipe_this_cpu_hrtimer_irq. And some ugly workaround in Xenomai for
>>>>> older I-pipe versions.
>>>>>
>>>>> Does this make sense?
>>>>
>>>> Made something similar for forge:
>>>> http://git.xenomai.org/?p=xenomai-gch.git;a=commitdiff;h=37ca257af466e7e5fbfb402b39f088487d048fd5;hp=a9971c363fd361b428f12200536bc5a01dff9c05
>>>
>>
>> Caution, this code is WIP. nktimer will have to move to the percpu
>> scheduler descriptor to complete this.
>
> That's nkclock in 2.6. Mostly a cosmetic issue, the interrupt name will
> not be properly printed, statistics are already per-cpu. Could be
> improved nevertheless.
>

My point is to tell you that what you look to in -forge regarding this 
area is in a state of flux. I'm not referring to 2.6, I'm focusing 
almost exclusively on 3.x these days.

> Is there an easy way to find out if we have per-CPU timers on some arch?
>

Why should we assume differently?

> Jan
>


-- 
Philippe.


  parent reply	other threads:[~2013-01-03 17:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 17:43 [Xenomai] XNARCH_TIMER_IRQ Jan Kiszka
2013-01-03 15:16 ` Gilles Chanteperdrix
2013-01-03 15:44   ` Jan Kiszka
2013-01-03 16:27     ` Philippe Gerum
2013-01-03 17:21       ` Gilles Chanteperdrix
2013-01-03 17:30         ` Philippe Gerum
2013-01-03 17:25       ` Jan Kiszka
2013-01-03 17:30         ` Gilles Chanteperdrix
2013-01-03 17:34         ` Philippe Gerum [this message]
2013-01-03 17:57           ` Jan Kiszka
2013-01-04 10:01             ` Philippe Gerum
2013-01-04 10:16               ` Jan Kiszka
2013-01-04 10:27                 ` Gilles Chanteperdrix
2013-01-04 10:32                 ` Philippe Gerum
2013-01-04 11:22                   ` Jan Kiszka
2013-01-04 11:33                     ` Philippe Gerum
2013-01-04 11:46                       ` Jan Kiszka
2013-01-04 12:54                         ` Philippe Gerum
2013-01-06 16:08                           ` Gilles Chanteperdrix
2013-01-06 23:02                             ` Jan Kiszka
2013-01-06 23:11                               ` Gilles Chanteperdrix
2013-01-06 23:13                                 ` 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=50E5C134.3010804@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=jan.kiszka@siemens.com \
    --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.