From: Greg KH <greg@kroah.com>
To: Mitch Williams <mitch.a.williams@intel.com>,
Michael Ellerman <michael@ellerman.id.au>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, gregkh@suse.de,
ebiederm@xmission.com, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, auke-jan.h.kok@intel.com
Subject: Re: [PATCH 2.6.21-rc5] MSI: read-flush MSI-X table
Date: Mon, 26 Mar 2007 17:09:51 -0700 [thread overview]
Message-ID: <20070327000951.GA11555@kroah.com> (raw)
In-Reply-To: <1174951102.22190.15.camel@strongmad>
On Mon, Mar 26, 2007 at 04:18:22PM -0700, Mitch Williams wrote:
> This patch fixes a kernel bug which is triggered when using the
> irqbalance daemon with MSI-X hardware.
>
> Because both MSI-X interrupt messages and MSI-X table writes are posted,
> it's possible for them to cross while in-flight. This results in
> interrupts being received long after the kernel thinks they're disabled,
> and in interrupts being sent to stale vectors after rebalancing.
>
> This patch performs a read flush after writes to the MSI-X table for
> enable/disable and rebalancing operations. Because this is an expensive
> operation, we do not perform the read flush after mask/unmask
> operations. Hardware which supports MSI-X typically also supports some
> sort of interrupt moderation, so a read-flush is not necessary for
> mask/unmask operations.
>
> This patch has been validated with (unreleased) network hardware which
> uses MSI-X.
How well does this play with the MSI core changes that Michael Ellerman
has proposed on the linux-pci mailing list?
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-27 0:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 23:18 Mitch Williams
2007-03-27 0:09 ` Greg KH [this message]
2007-03-27 2:26 ` Eric W. Biederman
2007-03-27 13:23 ` Eric W. Biederman
2007-03-27 14:55 ` Grant Grundler
2007-03-27 15:15 ` Eric W. Biederman
2007-03-27 15:25 ` Grant Grundler
2007-03-27 15:31 ` Williams, Mitch A
2007-03-27 16:01 ` Eric W. Biederman
2007-03-27 17:15 ` Williams, Mitch A
2007-03-27 21:13 ` Eric W. Biederman
2007-03-27 21:43 ` Williams, Mitch A
2007-03-28 1:14 ` Eric W. Biederman
2007-03-28 15:37 ` Williams, Mitch A
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=20070327000951.GA11555@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=michael@ellerman.id.au \
--cc=mitch.a.williams@intel.com \
/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
all inboxes | Powered by JetHome®