From: Lucas Stach <l.stach@pengutronix.de>
To: Fugang Duan <fugang.duan@nxp.com>, netdev@vger.kernel.org
Cc: patchwork-lst@pengutronix.de, kernel@pengutronix.de
Subject: [PATCH 1/2] net: fec: don't ack masked interrupt events
Date: Wed, 6 Dec 2017 18:24:58 +0100 [thread overview]
Message-ID: <20171206172459.14059-1-l.stach@pengutronix.de> (raw)
The FEC doesn't have a real interrupt status register, that takes
into account the mask status of the IRQ. The driver reads the raw
interrupt event register, which also reports events for masked
IRQs.
The driver needs to apply the current mask itself, to avoid acking
IRQs that are currently masked, as NAPI relies on the masking to
hide the IRQs. The current behavior of just acking all interrupts
regardless of their mask status opens the driver up the "rotting
packet" race-window, as described in the original NAPI-HOWTO, which
has been observed in the wild.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
drivers/net/ethernet/freescale/fec_main.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/freescale/fec_main.c b/drivers/net/ethernet/freescale/fec_main.c
index 610573855213..0b70c07eb703 100644
--- a/drivers/net/ethernet/freescale/fec_main.c
+++ b/drivers/net/ethernet/freescale/fec_main.c
@@ -1584,7 +1584,8 @@ fec_enet_interrupt(int irq, void *dev_id)
uint int_events;
irqreturn_t ret = IRQ_NONE;
- int_events = readl(fep->hwp + FEC_IEVENT);
+ int_events = readl_relaxed(fep->hwp + FEC_IEVENT) &
+ readl_relaxed(fep->hwp + FEC_IMASK);
writel(int_events, fep->hwp + FEC_IEVENT);
fec_enet_collect_events(fep, int_events);
--
2.11.0
next reply other threads:[~2017-12-06 17:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 17:24 Lucas Stach [this message]
2017-12-06 17:24 ` [PATCH 2/2] net: fec: optimize IRQ handler Lucas Stach
2017-12-07 3:02 ` Andy Duan
2017-12-06 20:47 ` [PATCH 1/2] net: fec: don't ack masked interrupt events David Miller
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=20171206172459.14059-1-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=fugang.duan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=patchwork-lst@pengutronix.de \
/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).