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] Registering MSI interrupt with Xenomai fails
Date: Sat, 03 Nov 2007 19:19:24 +0100 [thread overview]
Message-ID: <472CBBAC.7030403@domain.hid> (raw)
In-Reply-To: <fd6a47a90711031042j568938fev22c3b5a6f99d8e17@domain.hid>
Jeroen Van den Keybus wrote:
>
> arch_setup_msi_irq() creates an IRQ on-the-fly from the current
> descriptor which is being converted to an MSI interrupt using
> pci_msi_enable(). From that point, the I-pipe might have an obsolete
> view of the interrupt map. I suspect an I-pipe issue here.
>
>
>
> I think the I-pipe is alright. It only cares for the actual interrupt
> numbers and irq_desc[] should be current with these numbers upon the
> ipipe_virtualize_irq call, which occurs only after enabling MSI, right ?
>
The I-pipe virtualizes all IOAPIC and ISA interrupts upon startup. Then,
any code calling pci_msi_enable() would end up allocating a new MSI
interrupt vector.
> Currently it looks like every PCI config space access instruction in
> read_msi_msg() (used to perform set_msi_irq_affinity) freezes the
> machine. I have absolutely no clue yet why this happens.
>
Wild trivial guess, is the irq parameter the expected one, since the
rest depends on it?
> Jeroen.
>
>
> --
> Philippe.
>
>
--
Philippe.
next prev parent reply other threads:[~2007-11-03 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 11:21 [Xenomai-core] Registering MSI interrupt with Xenomai fails Jeroen Van den Keybus
2007-11-02 11:50 ` Philippe Gerum
[not found] ` <fd6a47a90711020549u5630ec9cgda7042c8c6c0f10a@domain.hid>
[not found] ` <fd6a47a90711020636t73e357d5ub9cbca0675adc1d7@domain.hid>
2007-11-02 14:30 ` Jeroen Van den Keybus
2007-11-02 14:59 ` Philippe Gerum
2007-11-03 17:42 ` Jeroen Van den Keybus
2007-11-03 18:19 ` Philippe Gerum [this message]
2007-11-03 19:36 ` Jeroen Van den Keybus
2007-11-05 19:14 ` Jeroen Van den Keybus
2007-11-12 14:43 ` Jeroen Van den Keybus
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=472CBBAC.7030403@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.