From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: rpm@xenomai.org
Cc: adeos-main <adeos-main@gna.org>, RTnet-users@domain.hid
Subject: Re: [Adeos-main] [RTnet-users] e1000 & MSI
Date: Thu, 14 Aug 2008 17:25:04 +0200 [thread overview]
Message-ID: <48A44E50.5040506@domain.hid> (raw)
In-Reply-To: <48A43555.3070701@domain.hid>
Philippe Gerum wrote:
>> (ipipe_check_context+0x94)
>> | +*func 0 find_next_bit+0xa (__next_cpu+0x1a)
>> | +*func 0 __next_cpu+0x9 (ipipe_check_context+0x88)
>> | +*func 0 find_next_bit+0xa (__next_cpu+0x1a)
>> | +*func 0 __next_cpu+0x9 (ipipe_check_context+0x88)
>> | +*func 0 find_next_bit+0xa (__next_cpu+0x1a)
>> | +*func 0 __next_cpu+0x9 (ipipe_check_context+0x88)
>> | +*func 0 find_next_bit+0xa (__next_cpu+0x1a)
>> | +*func 0 __next_cpu+0x9 (ipipe_check_context+0x88)
>> | +*func 0 find_first_bit+0xa (__first_cpu+0x12)
>> | +*func -1 __first_cpu+0x8 (ipipe_check_context+0x66)
>> | +*func -1 ipipe_check_context+0x14
>> (_spin_lock_irqsave+0x1e)
>> | +*func -1 _spin_lock_irqsave+0x12
>> (pci_bus_read_config_word+0x36)
>> | +*func -1 pci_bus_read_config_word+0x14
>> (__msi_set_enable+0x46)
>> | +*func -1 __msi_set_enable+0x14 (msi_set_mask_bits+0xd8)
>> | +*func -1 msi_set_mask_bits+0xe (unmask_msi_irq+0x17)
>> | +*func -1 unmask_msi_irq+0x9 (default_enable+0x1a)
>> | +*func -1 default_enable+0x9 (rt_enable_irq+0xe
Excuse my naive question: but for every MSI interrupts, we need to issue
a PCI read and look for some bits ? Is not this a bit insane ?
--
Gilles.
next prev parent reply other threads:[~2008-08-14 15:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080812075358.4cg1ix9945msccsc@domain.hid>
[not found] ` <48A12EA8.4070601@domain.hid>
[not found] ` <48A34D75.9090509@domain.hid>
2008-08-13 22:01 ` [Adeos-main] [RTnet-users] e1000 & MSI Jan Kiszka
2008-08-14 6:34 ` Jan Kiszka
2008-08-14 6:49 ` Jan Kiszka
2008-08-14 7:41 ` Philippe Gerum
2008-08-14 10:53 ` bernhard
2008-08-14 13:38 ` Philippe Gerum
2008-08-14 15:25 ` Gilles Chanteperdrix [this message]
2008-08-14 15:34 ` Bernhard Pfund
2008-08-14 15:52 ` Gilles Chanteperdrix
2008-08-14 16:57 ` Philippe Gerum
2008-08-16 11:24 ` Bernhard Pfund
2008-08-19 10:17 ` Philippe Gerum
2008-08-19 10:31 ` bernhard
2008-08-19 14:18 ` Philippe Gerum
2008-08-19 20:53 ` Bernhard Pfund
2008-08-20 9:38 ` Philippe Gerum
2008-08-25 12:16 ` bernhard
2008-08-25 12:58 ` Jan Kiszka
2008-08-25 13:48 ` bernhard
2008-08-25 14:15 ` Philippe Gerum
2008-08-14 17:35 ` Jan Kiszka
2008-08-14 17:55 ` Philippe Gerum
2008-08-14 18:21 ` 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=48A44E50.5040506@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=RTnet-users@domain.hid \
--cc=adeos-main@gna.org \
--cc=rpm@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.