From: Greg KH <gregkh@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Mitch Williams <mitch.a.williams@intel.com>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
auke-jan.h.kok@intel.com
Subject: Re: [PATCH 2.6.21-rc5] Flush MSI-X table writes (rev 3)
Date: Fri, 30 Mar 2007 12:49:56 -0700 [thread overview]
Message-ID: <20070330194956.GA8028@suse.de> (raw)
In-Reply-To: <20070330124747.f20c9eb0.akpm@linux-foundation.org>
On Fri, Mar 30, 2007 at 12:47:47PM -0700, Andrew Morton wrote:
> On Fri, 30 Mar 2007 13:04:02 -0600
> ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> > Mitch Williams <mitch.a.williams@intel.com> writes:
> >
> > > 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
> > > mask and unmask operations. Since the SMP affinity is set while
> > > the interrupt is masked, and since it's unmasked immediately after,
> > > no additional flushes are required in the various affinity setting
> > > routines.
> > >
> > > This patch has been validated with (unreleased) network hardware which
> > > uses MSI-X.
> > >
> > > Revised with input from Eric Biederman.
> >
> > Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
>
> Did we end up deciding whether this is (needed*safe) enough for 2.6.21?
I say no for now, I have seen no bug reports for any hardware that is
not in a lab for this.
thanks,
greg k-h
next prev parent reply other threads:[~2007-03-30 19:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 18:54 [PATCH 2.6.21-rc5] Flush MSI-X table writes (rev 3) Mitch Williams
2007-03-30 19:04 ` Eric W. Biederman
2007-03-30 19:47 ` Andrew Morton
2007-03-30 19:49 ` Greg KH [this message]
2007-03-30 20:00 ` Andrew Morton
2007-03-30 20:10 ` Greg KH
2007-03-30 20:21 ` Williams, Mitch A
2007-03-30 20:24 ` Greg KH
2007-03-30 20:26 ` Eric W. Biederman
2007-03-30 20:49 ` Williams, Mitch A
2007-03-30 20:56 ` Chuck Ebbert
2007-03-30 21:05 ` Eric W. Biederman
2007-04-03 7:41 ` [PATCH] msi: Immediately mask and unmask msi-x irqs Eric W. Biederman
2007-04-03 17:24 ` Williams, Mitch A
2007-04-03 18:52 ` Siddha, Suresh B
2007-04-03 19:39 ` Eric W. Biederman
2007-04-03 20:57 ` Siddha, Suresh B
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=20070330194956.GA8028@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=auke-jan.h.kok@intel.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--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