]> git.baikalelectronics.ru Git - kernel.git/commit
i40evf: don't fire traffic IRQs when the interface is down
authorMitch A Williams <mitch.a.williams@intel.com>
Tue, 9 Dec 2014 08:53:06 +0000 (08:53 +0000)
committerJeff Kirsher <jeffrey.t.kirsher@intel.com>
Tue, 13 Jan 2015 19:47:43 +0000 (11:47 -0800)
commit12e4f51ac4bb5e08520cdff4711952e25d65a6f7
tree6140a77e60f85bbdd6dfcdda97768d6f113c7d74
parent3c90897a82377b10c6daf28b1070c9a31bc30029
i40evf: don't fire traffic IRQs when the interface is down

There is always a possibility that MSI-X interrupts can get lost. To
keep this problem from stalling the driver, we fire all of our MSI-X
vectors during the watchdog routine. However, we should not fire the
traffic vectors when the interface is closed. In this case, just fire
vector 0, which is used for admin queue events.

As a result, we do not enable the interrupt cause for vector 0. This
can cause the admin queue handler to be called reentrantly, which
causes a scary "critical section violation" message to be logged,
even though no real damage is done.

Change-ID: Ic43a5184708ab2cb9a23fca7dedd808a46717795
Signed-off-by: Mitch Williams <mitch.a.williams@intel.com>
Acked-by: Shannon Nelson <shannon.nelson@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
drivers/net/ethernet/intel/i40evf/i40evf_main.c