Thread (1 message) 1 message, 1 author, 2014-04-23

RE: [Patch 3/3] IB/ib_cm: hang in cm_destroy_id during PCI error injection

From: Hefty, Sean <hidden>
Date: 2014-04-23 21:34:55
Also in: linux-rdma

quoted
This is a device level event, not a port event.  The port_num value may
not be valid.
The first patch of the series(IB/mlx4: send a IB_EVENT_DEVICE_FATAL to
users during PCI error injection), when mlx4 send the IB_EVENT_DEVICE_FATAL
event I am passing the port number to that field so in that way I was
able to make it work. Any other suggestions are welcome.
This would need to be done for all devices.

Converting this to a per port event requires multiple events per device, which would impact the user space ABI.  I think the patch itself needs to change to remove the per port association and operate at the device level, since it is really a device event. 
--
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help