From: Benjamin Poirier <bpoirier@suse.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] e1000e: Revert interrupt handling changes
Date: Fri, 26 Jan 2018 18:12:33 +0900 [thread overview]
Message-ID: <20180126091236.13044-1-bpoirier@suse.com> (raw)
As discussed in the thread "[RFC PATCH] e1000e: Remove Other from EIAC.",
https://www.spinics.net/lists/netdev/msg479311.html
The following list of commits was considered:
4d432f67ff00 e1000e: Remove unreachable code (v4.5-rc1)
16ecba59bc33 e1000e: Do not read ICR in Other interrupt (v4.5-rc1)
a61cfe4ffad7 e1000e: Do not write lsc to ics in msi-x mode (v4.5-rc1)
0a8047ac68e5 e1000e: Fix msi-x interrupt automask (v4.5-rc1)
19110cfbb34d e1000e: Separate signaling for link check/link up (v4.15-rc1)
4aea7a5c5e94 e1000e: Avoid receiver overrun interrupt bursts (v4.15-rc1)
4110e02eb45e e1000e: Fix e1000_check_for_copper_link_ich8lan return value. (v4.15-rc8)
There have a been a slew of regressions due to unforeseen consequences
(receive overflow triggers Other, vmware's emulated e1000e) and programming
mistakes (4110e02eb45e). Since the e1000e driver is supposed to be in
maintenance mode, this patch series revisits the above changes to prune
them down.
After this series, the remaining differences related to how interrupts were
handled at commit 4d432f67ff00 ("e1000e: Remove unreachable code",
v4.5-rc1) are:
* the changes in commit 0a8047ac68e5 ("e1000e: Fix msi-x interrupt
automask", v4.5-rc1) are preserved.
* we manually clear Other from icr in e1000_msix_other().
We try to go back to a long lost time when things were simple and drivers
ran smoothly.
----------------------------------------------------------------
Benjamin Poirier (3):
Partial revert "e1000e: Avoid receiver overrun interrupt bursts"
Revert "e1000e: Separate signaling for link check/link up"
Revert "e1000e: Do not read ICR in Other interrupt"
drivers/net/ethernet/intel/e1000e/defines.h | 1 -
drivers/net/ethernet/intel/e1000e/ich8lan.c | 11 ++------
drivers/net/ethernet/intel/e1000e/mac.c | 11 ++------
drivers/net/ethernet/intel/e1000e/netdev.c | 44 ++++++++++++++---------------
4 files changed, 27 insertions(+), 40 deletions(-)
--
2.15.1
next reply other threads:[~2018-01-26 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 9:12 Benjamin Poirier [this message]
2018-01-26 9:12 ` [PATCH 1/3] Partial revert "e1000e: Avoid receiver overrun interrupt bursts" Benjamin Poirier
2018-01-26 16:50 ` Alexander Duyck
2018-01-29 7:20 ` Benjamin Poirier
2018-01-29 15:42 ` Alexander Duyck
2018-01-26 9:12 ` [PATCH 2/3] Revert "e1000e: Separate signaling for link check/link up" Benjamin Poirier
2018-01-26 17:03 ` Alexander Duyck
2018-01-29 7:21 ` Benjamin Poirier
2018-01-29 15:48 ` Alexander Duyck
2018-02-26 2:31 ` [RFC PATCH] e1000e: Fix link check race condition Benjamin Poirier
2018-02-26 16:14 ` Alexander Duyck
2018-02-28 5:19 ` Benjamin Poirier
2018-01-26 9:12 ` [PATCH 3/3] Revert "e1000e: Do not read ICR in Other interrupt" Benjamin Poirier
2018-01-26 21:01 ` Alexander Duyck
2018-01-29 7:28 ` Benjamin Poirier
2018-01-29 17:22 ` Alexander Duyck
2018-02-08 6:40 ` Benjamin Poirier
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=20180126091236.13044-1-bpoirier@suse.com \
--to=bpoirier@suse.com \
--cc=alexander.duyck@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®