From: Karen Shaeffer <shaeffer@neuralscape.com>
To: Ayaz Abdulla <AAbdulla@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
jgarzik@pobox.com, manfred@colorfullife.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] forcedeth: msi interrupts
Date: Fri, 6 Jun 2008 14:40:16 -0700 [thread overview]
Message-ID: <20080606214016.GA3345@synapse.neuralscape.com> (raw)
In-Reply-To: <F72FA20C31DD4F4C997B91C5B3690A090B146100@hqemmail07.nvidia.com>
On Fri, Jun 06, 2008 at 02:19:31PM -0700, Ayaz Abdulla wrote:
> Yes, that would be great!
Hi Ayaz,
How far back should it be back ported? Do you know?
Thanks,
Karen
>
> -----Original Message-----
> From: Andrew Morton [mailto:akpm@linux-foundation.org]
> Sent: Friday, June 06, 2008 2:11 PM
> To: Ayaz Abdulla
> Cc: jgarzik@pobox.com; manfred@colorfullife.com; netdev@vger.kernel.org
> Subject: Re: [PATCH] forcedeth: msi interrupts
>
>
> On Fri, 06 Jun 2008 14:04:05 -0400
> Ayaz Abdulla <aabdulla@nvidia.com> wrote:
>
> >
> >
> > Andrew Morton wrote:
> > > On Fri, 06 Jun 2008 13:15:32 -0400
> > > Ayaz Abdulla <aabdulla@nvidia.com> wrote:
> > >
> > >
> > >>Andrew Morton wrote:
> > >>
> > >>>On Tue, 03 Jun 2008 16:51:46 -0400
> > >>>Ayaz Abdulla <aabdulla@nvidia.com> wrote:
> > >>>
> > >>> > This patch adds a workaround for lost MSI interrupts. There is a
> race
> > >>> > condition in the HW in which future interrupts could be missed.
> The
> > >>> > workaround is to toggle the MSI irq mask.
> > >>> >
> > >>>
> > >>>Do you think this is a 2.6.26 thing?
> > >>
> > >>It is by HW design, not related to the kernel.
> > >
> > >
> > > Sorry, what I meant was: do you believe that this patch should be in
> > > 2.6.26?
> > Yes, it should be treated as a critical fix.
>
> So should it also be backported into 2.6.25.x?
>
> Bear in mind that $major_distros are apparently basing product on
> 2.6.25.
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may contain
> confidential information. Any unauthorized review, use, disclosure or distribution
> is prohibited. If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
> -----------------------------------------------------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
---end quoted text---
--
Karen Shaeffer
Neuralscape, Palo Alto, Ca. 94306
shaeffer@neuralscape.com http://www.neuralscape.com
next prev parent reply other threads:[~2008-06-06 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 20:51 [PATCH] forcedeth: msi interrupts Ayaz Abdulla
2008-06-04 22:18 ` Andrew Morton
2008-06-04 23:00 ` Karen Shaeffer
2008-06-06 17:15 ` Ayaz Abdulla
2008-06-06 20:19 ` Andrew Morton
2008-06-06 18:04 ` Ayaz Abdulla
2008-06-06 21:10 ` Andrew Morton
2008-06-06 21:19 ` Ayaz Abdulla
2008-06-06 21:40 ` Karen Shaeffer [this message]
2008-06-07 18:31 ` Karen Shaeffer
2008-06-07 19:28 ` Ayaz Abdulla
2008-06-08 1:33 ` Karen Shaeffer
2008-06-08 2:01 ` Karen Shaeffer
2008-06-07 19:24 ` Ayaz Abdulla
2008-06-06 18:03 ` Ayaz Abdulla
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=20080606214016.GA3345@synapse.neuralscape.com \
--to=shaeffer@neuralscape.com \
--cc=AAbdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=jgarzik@pobox.com \
--cc=manfred@colorfullife.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).