From: Philippe Gerum <rpm@xenomai.org>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Interrupt latency close to 1ms on powerpc Xenomai 2.6.4
Date: Thu, 8 Oct 2015 19:34:16 +0200 [thread overview]
Message-ID: <5616A918.6030607@xenomai.org> (raw)
In-Reply-To: <20151008154735.GG8324@hermes.click-hack.org>
On 10/08/2015 05:47 PM, Gilles Chanteperdrix wrote:
> On Thu, Oct 08, 2015 at 05:41:41PM +0200, Philippe Gerum wrote:
>> On 10/08/2015 05:17 PM, Lennart Sorensen wrote:
>>> On Thu, Oct 08, 2015 at 04:54:07PM +0200, Philippe Gerum wrote:
>>>> I could not find one that would not look weird. That logic is deeply
>>>> buried in kernel space, and introducing a dynamic dependency on whether
>>>> e.g. the PCI layer has to be traversed for carrying out such ops would
>>>> be rather confusing for the end user, especially when porting the
>>>> application code over different SoCs.
>>>
>>> Yep, that sounds ugly.
>>>
>>>> Likely, yes. The relevant handlers dealing with the interrupt controller
>>>> of the QUICC Engine do not tread on problematic code, so this should be
>>>> ok for this platform.
>>>
>>> Then I have the icky situation that we want the same kernel source to
>>> run on arm. I wonder if the am572x would care. I guess I could #ifdef
>>> it for powerpc only and leave the new way on arm.
>>>
>>
>> No guarantee, I only had a quick look at this, but AFAICS:
>>
>> - the irqchip from the PCA953X gpio extender module does not seem to
>> have any requirement for running over a regular kernel context
>>
>> - the main GIC IRQ controller is fine, since the fast ack code we use
>> over the head domain is shared with the IRQ enabling/disabling support.
>>
>> So this should be ok (famous last words).
>
> The GIC has some board/SOC specific callbacks, so, you have to check
> these callbacks too, to be sure that the code does not use some
> linux services.
>
On the dra7xx Lennart is working on, this is not an issue. The pipeline
is traversing them (or maybe none of them actually) in primary mode happily.
--
Philippe.
next prev parent reply other threads:[~2015-10-08 17:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 15:35 [Xenomai] Interrupt latency close to 1ms on powerpc Xenomai 2.6.4 PRADHAN, MAKARAND (RC-CA)
2015-09-29 15:50 ` Philippe Gerum
2015-09-29 16:04 ` PRADHAN, MAKARAND (RC-CA)
2015-09-29 16:15 ` Philippe Gerum
2015-09-29 17:14 ` PRADHAN, MAKARAND (RC-CA)
2015-10-02 18:30 ` PRADHAN, MAKARAND (RC-CA)
2015-10-02 20:23 ` PRADHAN, MAKARAND (RC-CA)
2015-10-07 14:25 ` PRADHAN, MAKARAND (RC-CA)
2015-10-07 18:47 ` Philippe Gerum
2015-10-07 18:55 ` Philippe Gerum
2015-10-07 19:27 ` PRADHAN, MAKARAND (RC-CA)
2015-10-07 19:32 ` Lennart Sorensen
2015-10-08 6:50 ` Philippe Gerum
2015-10-08 14:43 ` Lennart Sorensen
2015-10-08 14:52 ` Gilles Chanteperdrix
2015-10-08 15:15 ` Lennart Sorensen
2015-10-08 20:19 ` Lennart Sorensen
2015-10-08 20:27 ` Gilles Chanteperdrix
2015-10-08 20:30 ` Lennart Sorensen
2015-10-08 20:31 ` Gilles Chanteperdrix
2015-10-08 20:41 ` Lennart Sorensen
2015-10-08 14:54 ` Philippe Gerum
2015-10-08 15:05 ` PRADHAN, MAKARAND (RC-CA)
2015-10-08 15:17 ` Lennart Sorensen
2015-10-08 15:41 ` Philippe Gerum
2015-10-08 15:47 ` Gilles Chanteperdrix
2015-10-08 17:34 ` Philippe Gerum [this message]
2015-10-08 15:51 ` Lennart Sorensen
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=5616A918.6030607@xenomai.org \
--to=rpm@xenomai.org \
--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.