From: Philippe Gerum <rpm@xenomai.org>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@domain.hid>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Handling PCI MSI interrupts
Date: Wed, 15 Feb 2006 23:48:49 +0100 [thread overview]
Message-ID: <43F3AFD1.3030807@domain.hid> (raw)
In-Reply-To: <fd6a47a90602151250k4eb0b3b0s@domain.hid>
Jeroen Van den Keybus wrote:
> It's definitely an Adeos issue and msi.c needs fixing. What about
> this patch, do
> things improve with it (against 2.6.15-ipipe-1.2-00)?
>
> I going to try the patch later on. I have currently a ´fully
> instrumented´ kernel against which this patch would not ever work... I´m
> keeping that kernel for now, because I´m also investigating why MSI also
> doesn´t work under RTDM. It´s merely a coincidence that the above bug
> (MSI interrupts from Linux devices getting blocked) emerged and produced
> exactly the same behaviour (system hanging).
>
> But, normally, that path is not used in RT mode, is it ? So something
> else is getting in the way.
>
> At the first look of it, I´m a bit wary of touching that msi.c . I was
> rather thinking of kicking out __ack_APIC() altogether ? Or is that not
> possible ? (I see only problems in p4.c and smp.c - but I haven´t looked
> at these very closely.)
>
>
We do need __ack_APIC_irq() to run the actual APIC ack code all over the place in
the APIC/IO-APIC support code, so that former regular uses of ack_APIC_irq() can
be left untouched. Adeos already changes significant areas within Linux's innards
in order to control its interrupt sub-system anyway, which in turn hides the gory
details of interrupt prioritization to client software like Xenomai.
drivers/pci/msi.c simply brings a new set of interrupt controllers we need to make
Adeos-aware, just like it has been done for the i8259, the LAPIC and the IO-APIC
supports.
--
Philippe.
next prev parent reply other threads:[~2006-02-15 22:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 15:44 [Xenomai-core] Handling PCI MSI interrupts Jeroen Van den Keybus
2006-02-14 17:50 ` Philippe Gerum
2006-02-14 18:07 ` Jeroen Van den Keybus
2006-02-14 18:17 ` Jan Kiszka
2006-02-14 18:26 ` Philippe Gerum
2006-02-14 18:52 ` Jeroen Van den Keybus
2006-02-14 19:22 ` Jeroen Van den Keybus
2006-02-14 19:33 ` Jeroen Van den Keybus
2006-02-14 21:41 ` Jeroen Van den Keybus
2006-02-14 21:56 ` Philippe Gerum
2006-02-15 11:00 ` Jeroen Van den Keybus
2006-02-15 18:02 ` Jeroen Van den Keybus
2006-02-15 18:34 ` Jeroen Van den Keybus
2006-02-15 20:09 ` Philippe Gerum
2006-02-15 20:50 ` Jeroen Van den Keybus
2006-02-15 22:48 ` Philippe Gerum [this message]
2006-02-15 22:58 ` Jeroen Van den Keybus
2006-02-15 23:09 ` Russell Johnson
2006-02-16 9:36 ` Philippe Gerum
2006-02-16 14:23 ` Russell Johnson
2006-02-17 12:54 ` Jeroen Van den Keybus
2006-02-17 13:08 ` Philippe Gerum
2006-02-17 14:43 ` Russell Johnson
2006-02-17 15:45 ` Philippe Gerum
2006-02-17 15:57 ` Jeroen Van den Keybus
2006-02-17 16:07 ` Philippe Gerum
2006-02-17 16:49 ` Jeroen Van den Keybus
2006-02-17 18:37 ` Jeroen Van den Keybus
2006-02-17 18:39 ` Philippe Gerum
2006-02-19 18:50 ` Philippe Gerum
2006-02-14 18:23 ` 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=43F3AFD1.3030807@domain.hid \
--to=rpm@xenomai.org \
--cc=jeroen.vandenkeybus@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.