From: Jan Kiszka <jan.kiszka@domain.hid>
To: Richard Cochran <richardcochran@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Stuck MSI in normal Linux driver
Date: Fri, 04 Mar 2011 09:16:28 +0100 [thread overview]
Message-ID: <4D709FDC.5030402@domain.hid> (raw)
In-Reply-To: <20110304081121.GA12640@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
On 2011-03-04 09:11, Richard Cochran wrote:
> On Fri, Mar 04, 2011 at 08:51:00AM +0100, Philippe Gerum wrote:
>>
>> I'm not saying this would be impossible to enable MSIs there, I'm just
>> saying that so far: nobody cared. Terrae incognitae.
>
> I care!
>
> When the first MSI interrupt from my PCIe card should arrive, running
> on a P2020RBD, the machine locks up. My BDI shows me that both cores
> are going round in circles.
>
> * core 1
> __ipipe_check_percpu_access () at kernel/ipipe/core.c:2067
> ipipe_suspend_domain () at kernel/ipipe/core.c:826
> __ipipe_check_percpu_access () at arch/powerpc/include/asm/ipipe_hwirq.h:57
> ipipe_suspend_domain () at kernel/ipipe/core.c:860
> cpu_idle () at arch/powerpc/kernel/idle.c:64
> ipipe_suspend_domain () at arch/powerpc/include/asm/ipipe_hwirq.h:57
>
> * core 2
> ipipe_suspend_domain () at kernel/ipipe/core.c:858
> cpu_idle () at arch/powerpc/kernel/idle.c:64
> ipipe_suspend_domain () at arch/powerpc/include/asm/ipipe_hwirq.h:57
>
> Any thoughts?
Well, if PPC masks MSIs on ack, you may run on a bug check or on an
already acquired Linux spin lock.
Independent of the need to add RT-safe mask/unmask support for MSIs
midterm, you likely first of all want to get rid of this masking in the
fast-path. I suspect it's not needed, also on PPC.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-03-04 8:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 15:16 [Xenomai-help] Stuck MSI in normal Linux driver Richard Cochran
2011-03-02 15:26 ` Gilles Chanteperdrix
2011-03-02 15:34 ` Richard Cochran
2011-03-02 15:38 ` Gilles Chanteperdrix
2011-03-02 18:18 ` Jan Kiszka
2011-03-03 7:21 ` Richard Cochran
2011-03-03 7:32 ` Philippe Gerum
2011-03-03 12:25 ` Wolfgang Grandegger
2011-03-03 12:30 ` Jan Kiszka
2011-03-03 12:54 ` Philippe Gerum
2011-03-03 23:45 ` Jan Kiszka
2011-03-04 7:51 ` Philippe Gerum
2011-03-04 8:09 ` Jan Kiszka
2011-03-04 8:30 ` Richard Cochran
2011-03-04 8:36 ` Jan Kiszka
2011-03-04 8:11 ` Richard Cochran
2011-03-04 8:16 ` Jan Kiszka [this message]
2011-03-07 9:26 ` Richard Cochran
2011-03-07 16:37 ` Philippe Gerum
2011-03-07 18:33 ` Richard Cochran
2011-03-08 7:55 ` Richard Cochran
2011-03-07 18:39 ` Gilles Chanteperdrix
2011-03-07 21:47 ` Philippe Gerum
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=4D709FDC.5030402@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=richardcochran@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.