From: Loic Prylli <loic@myri.com>
To: linux-pci@atrey.karlin.mff.cuni.cz,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: MSI problem since 2.6.21 for devices not providing a mask in their MSI capability
Date: Wed, 03 Oct 2007 17:12:27 -0400 [thread overview]
Message-ID: <470405BB.2000208@myri.com> (raw)
Hi,
We observe a problem with MSI since kernel 2.6.21 where interrupts would
randomly stop working. We have tracked it down to the new
msi_set_mask_bit definition in 2.6.21. In the MSI case with a device not
providing a "native" MSI mask, it was a no-op before, and now it
disables MSI in the MSI-ctl register which according to the PCI spec is
interpreted as reverting the device to legacy interrupts. If such a
device try to generate a new interrupt during the "masked" window, the
device will try a legacy interrupt which is generally
ignored/never-acked and cause interrupts to no longer work for the
device/driver combination (even after the enable bit is restored).
Is there anything apart from irq migration that strongly requires
masking? Is is possible to do the irq migration without masking?
Loic
next reply other threads:[~2007-10-03 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 21:12 Loic Prylli [this message]
2007-10-03 21:49 ` MSI problem since 2.6.21 for devices not providing a mask in their MSI capability Eric W. Biederman
2007-10-03 22:03 ` Benjamin Herrenschmidt
2007-10-03 22:25 ` Eric W. Biederman
2007-10-04 1:44 ` Loic Prylli
2007-10-04 3:58 ` Eric W. Biederman
2007-10-04 9:14 ` Loic Prylli
2007-10-04 17:03 ` Eric W. Biederman
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=470405BB.2000208@myri.com \
--to=loic@myri.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox