From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] MSI Interrupt Crash
Date: Fri, 02 May 2008 12:09:20 +0200 [thread overview]
Message-ID: <481AE850.8090807@domain.hid> (raw)
In-Reply-To: <481AE503.2060609@domain.hid>
Jan Kiszka wrote:
> Philippe Gerum wrote:
>> PS: We really do want to call mask/unmask instead of disable/enable in any case, because ->disable()
>> became a nop in 2.6.21, so we just can't rely on its default action anyway. This is a separate
>> issue, that caused rthal_irq_disable() not to actually mask the interrupt when the I/O APIC is enabled.
>
> Hmmmm... That makes me scratch my head. Could this change have some
> impact on I-pipe as well? We are currently pulling hairs here as some
> SCSI adapter is flooding us with spurious IRQs during init, but only if
> I-pipe is enabled.
>
__ipipe_enable_irq/__ipipe_disable_irq are not doing the right thing anymore,
but, AFAICT, this would only affect callers of ipipe_virtualize_irq and
ipipe_control_irq, using IPIPE_ENABLE_MASK.
Btw, are those APIC-based SMP spurious interrupts, or 8259-based ones?
--
Philippe.
next prev parent reply other threads:[~2008-05-02 10:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 5:29 [Xenomai-help] MSI Interrupt Crash jeff koftinoff
2008-05-02 7:56 ` Philippe Gerum
2008-05-02 8:50 ` Jan Kiszka
2008-05-02 9:04 ` Philippe Gerum
2008-05-02 9:07 ` Jan Kiszka
2008-05-02 9:40 ` Philippe Gerum
2008-05-02 9:55 ` Jan Kiszka
2008-05-02 10:09 ` Philippe Gerum [this message]
2008-05-02 10:42 ` Jan Kiszka
2008-05-02 10:53 ` Philippe Gerum
2008-05-05 11:17 ` Jan Kiszka
2008-05-02 9:40 ` Philippe Gerum
2008-05-02 14:17 ` Thomas Schaefer
2008-05-02 15:02 ` Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2008-05-02 16:26 Thomas Schaefer
2008-05-04 8:46 ` 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=481AE850.8090807@domain.hid \
--to=rpm@xenomai.org \
--cc=jan.kiszka@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.