From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] e1000e: Remove Other from EIAC.
Date: Thu, 18 Jan 2018 16:41:20 +0900 [thread overview]
Message-ID: <20180118074120.j7qbmapusiypsvsq@f1.synalogic.ca> (raw)
In-Reply-To: <20180118065054.29844-1-bpoirier@suse.com>
On 2018/01/18 15:50, Benjamin Poirier wrote:
> It was reported that emulated e1000e devices in vmware esxi 6.5 Build
> 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid receiver
> overrun interrupt bursts", v4.15-rc1). Some tracing shows that after
> e1000e_trigger_lsc() is called, ICR reads out as 0x0 in e1000_msix_other()
> on emulated e1000e devices. In comparison, on real e1000e 82574 hardware,
> icr=0x80000004 (_INT_ASSERTED | _OTHER) in the same situation.
(_INT_ASSERTED | _LSC)
>
> Some experimentation showed that this flaw in vmware e1000e emulation can
> be worked around by not setting Other in EIAC. This is how it was before
> 16ecba59bc33 ("e1000e: Do not read ICR in Other interrupt", v4.5-rc1).
>
> Fixes: 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts")
> Signed-off-by: Benjamin Poirier <bpoirier@suse.com>
next prev parent reply other threads:[~2018-01-18 7:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 6:50 [RFC PATCH] e1000e: Remove Other from EIAC Benjamin Poirier
2018-01-18 7:27 ` Benjamin Poirier
2018-01-19 2:42 ` Shrikrishna Khare
2018-01-19 5:36 ` Benjamin Poirier
2018-01-18 7:41 ` Benjamin Poirier [this message]
2018-01-18 15:51 ` [Intel-wired-lan] " Alexander Duyck
2018-01-19 8:59 ` Benjamin Poirier
2018-01-19 13:36 ` Benjamin Poirier
2018-01-19 16:22 ` Alexander Duyck
2018-01-19 22:45 ` Benjamin Poirier
2018-01-19 22:55 ` Benjamin Poirier
2018-01-20 17:21 ` Alexander Duyck
2018-01-22 7:12 ` Benjamin Poirier
2018-01-22 18:01 ` Alexander Duyck
2018-01-24 8:35 ` Benjamin Poirier
2018-01-24 16:01 ` Alexander Duyck
2018-01-30 19:46 ` Alexander Duyck
2018-01-31 7:31 ` Benjamin Poirier
2018-02-02 4:29 ` Brown, Aaron F
2018-02-02 4:31 ` Brown, Aaron F
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=20180118074120.j7qbmapusiypsvsq@f1.synalogic.ca \
--to=benjamin.poirier@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;
as well as URLs for NNTP newsgroup(s).