Re: [PATCH net-next V0 18/21] mlx4_core: adjust catas operation for SRIOV mode

On Fri, Dec 2, 2011 at 2:19 AM, Yevgeny Petrilin
[off-list ref] wrote:

When running in SRIOV mode, driver should not automatically start/stop
the mlx4_core upon sensing an HCA internal error -- doing this disables/enables
sriov, which will cause the hypervisor to hang if there are running VMs with
attached VFs.

Not sure I understand this -- what happens if the driver doesn't reset
the device
after a catastrophic error?  Surely all the VFs are pretty screwed at
that point?

Which hypervisor are we talking about here anyway?

 - R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html