From: David Miller <davem@davemloft.net>
To: mcarlson@broadcom.com
Cc: netdev@vger.kernel.org, mchan@broadcom.com, benli@broadcom.com,
andy@greyhouse.net
Subject: Re: [PATCH 2/8] tg3: Allow screaming interrupt detection
Date: Tue, 21 Apr 2009 01:41:58 -0700 (PDT) [thread overview]
Message-ID: <20090421.014158.190780360.davem@davemloft.net> (raw)
In-Reply-To: <1240247955.7012@xw6200>
From: "Matt Carlson" <mcarlson@broadcom.com>
Date: Mon, 20 Apr 2009 09:55:01 -0700
> The tg3 driver's ISR is coded to accept interrupts as its own if the
> status block tag does not equal the last tag the driver has seen. The
> last_tag field is updated from tg3_poll. In a screaming interrupt
> situation from another device sharing tg3's IRQ, tg3_poll does not get
> a chance to be called, so the last_tag will always be out of sync with
> the status block tag. Consequently, the driver will continually
> declare the screaming interrupts as its own, thus thwarting the
> screaming interrupt detection logic.
>
> This patch solves the problem by creating a new last_irq_tag member and
> recording the status block tag in the ISR. The ISR then checks the
> last_irq_tag for interrupt ownership.
>
> Many thanks to John Marvin for the detailed bug report and analysis and
> Michael Chan for the bugfix.
>
> Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
> Tested-by: John Marvin <jsm@fc.hp.com>
Applied.
prev parent reply other threads:[~2009-04-21 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 16:55 [PATCH 2/8] tg3: Allow screaming interrupt detection Matt Carlson
2009-04-21 8:41 ` David Miller [this message]
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=20090421.014158.190780360.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=benli@broadcom.com \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.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).