From: Philippe Gerum <rpm@xenomai.org>
To: "M. Koehrer" <mathias_koehrer@domain.hid>
Cc: xenomai@xenomai.org, jan.kiszka@domain.hid
Subject: Re: [Xenomai-help] Xenomai and MSI enabled crashes kernel
Date: Fri, 04 May 2007 15:03:01 +0200 [thread overview]
Message-ID: <1178283781.29093.98.camel@domain.hid> (raw)
In-Reply-To: <20127779.1178282801939.JavaMail.ngmail@domain.hid>
On Fri, 2007-05-04 at 14:46 +0200, M. Koehrer wrote:
> Hi Philippe,
>
> I patched the create_irq() function to start the search for unused interrupts not at
> NR_IRQS -1 but from 127.
> And this seems actually to work.
> It looks like the right track!
> That means, that actually the large IRQ numbers are conflicting with the system
> interrupts.
> However, I wonder why this works with a non-adeos-patched kernel...
Because the vanilla kernel does not need to map system vectors to
interrupt numbers.
>
> Regards
>
> Mathias
>
>
> >
> > No, the trampoline code in entry.S passes us an irq actually. But there
> > is indeed a vector:irq mapping issue with IRQ numbers greater than 206,
> > which still badly conflict with system IRQs (MSI causes high numbered
> > IRQs to be allocated). I'm working on a patch. More later.
> >
>
>
--
Philippe.
next prev parent reply other threads:[~2007-05-04 13:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 7:45 [Xenomai-help] Xenomai and MSI enabled crashes kernel M. Koehrer
2007-05-04 7:59 ` Jan Kiszka
2007-05-04 8:20 ` M. Koehrer
2007-05-04 12:20 ` Philippe Gerum
2007-05-04 12:46 ` M. Koehrer
2007-05-04 13:03 ` Philippe Gerum [this message]
2007-05-05 17:21 ` Philippe Gerum
2007-05-08 11:53 ` M. Koehrer
2007-05-08 12:28 ` Philippe Gerum
2007-05-08 12:38 ` M. Koehrer
2007-05-08 13:28 ` Philippe Gerum
2007-05-08 13:37 ` Philippe Gerum
2007-05-08 14:35 ` M. Koehrer
2007-05-09 8:00 ` Philippe Gerum
-- strict thread matches above, loose matches on Subject: below --
2007-05-07 7:11 M. Koehrer
2007-05-02 12:57 M. Koehrer
2007-05-02 13:23 ` Jan Kiszka
2007-05-02 14:47 ` Philippe Gerum
2007-05-03 7:06 ` M. Koehrer
2007-05-03 8:29 ` Philippe Gerum
2007-04-26 12:04 M. Koehrer
2007-04-27 11:48 ` Jan Kiszka
2007-04-27 13:14 ` Philippe Gerum
2007-04-27 13:22 ` Jan Kiszka
2007-04-27 13:31 ` M. Koehrer
2007-04-27 13:47 ` Jan Kiszka
2007-04-27 14:08 ` M. Koehrer
2007-04-27 14:19 ` Philippe Gerum
2007-04-27 14:28 ` M. Koehrer
2007-04-27 14:40 ` Philippe Gerum
2007-04-27 14:56 ` Philippe Gerum
2007-04-27 15:05 ` Philippe Gerum
2007-04-27 15:10 ` M. Koehrer
2007-04-27 15:36 ` Philippe Gerum
2007-04-27 15:41 ` M. Koehrer
2007-04-30 9:05 ` Jan Kiszka
2007-04-30 10:11 ` M. Koehrer
2007-04-30 11:27 ` Jan Kiszka
2007-04-30 12:51 ` M. Koehrer
2007-04-30 15:10 ` Jan Kiszka
2007-04-27 20:39 ` Philippe Gerum
2007-04-30 15:39 ` Philippe Gerum
2007-05-02 7:05 ` M. Koehrer
2007-05-02 8:39 ` Jan Kiszka
2007-05-02 9:14 ` M. Koehrer
2007-05-02 9:39 ` Jan Kiszka
2007-05-02 12:42 ` Philippe Gerum
2007-05-02 13:44 ` M. Koehrer
2007-05-02 13:49 ` Jan Kiszka
2007-04-27 14:31 ` Jan Kiszka
2007-04-27 14:52 ` M. Koehrer
2007-04-28 12:54 ` Bernhard Walle
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=1178283781.29093.98.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=jan.kiszka@domain.hid \
--cc=mathias_koehrer@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.