summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorBenjamin Poirier <bpoirier@suse.com>2018-01-31 10:26:27 +0300
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>2018-03-05 20:30:14 +0300
commit745d0bd3af99ccc8c5f5822f808cd133eadad6ac (patch)
treee45d04f8c9cab10bb57ebf98b11ba88e2cecfcb9 /tools/perf/scripts/python/export-to-sqlite.py
parenta7f0fb1bfb66ded5d556d6723d691b77a7146b6f (diff)
downloadlinux-745d0bd3af99ccc8c5f5822f808cd133eadad6ac.tar.xz
e1000e: Remove Other from EIAC
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 | _LSC) in the same situation. 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> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions