David Vrabel 42b5212fee xen-netback: stop the guest rx thread after a fatal error ... After commit e9d8b2c296 (xen-netback: disable rogue vif in kthread context), a fatal (protocol) error would leave the guest Rx thread spinning, wasting CPU time. Commit ecf08d2dbb (xen-netback: reintroduce guest Rx stall detection) made this even worse by removing a cond_resched() from this path. Since a fatal error is non-recoverable, just allow the guest Rx thread to exit. This requires taking additional refs to the task so the thread exiting early is handled safely. Signed-off-by: David Vrabel <david.vrabel@citrix.com> Reported-by: Julien Grall <julien.grall@linaro.org> Tested-by: Julien Grall <julien.grall@linaro.org> Acked-by: Wei Liu <wei.liu2@citrix.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2015-02-02 19:39:04 -08:00
..
common.h	xen-netback: support frontends without feature-rx-notify again	2014-12-18 12:49:49 -05:00
interface.c	xen-netback: stop the guest rx thread after a fatal error	2015-02-02 19:39:04 -08:00
Makefile
netback.c	xen-netback: stop the guest rx thread after a fatal error	2015-02-02 19:39:04 -08:00
xenbus.c	xen-netback: fixing the propagation of the transmit shaper timeout	2015-01-06 14:17:37 -05:00